|Version 2 (modified by stoecker, 20 months ago) (diff)|
Налаштування > Параметри з’єднання
Table of Contents
- The URL to the OSM server
- Authentication Settings
- Proxy Settings
The URL to the OSM server
Downloading and uploading to the default server
Most JOSM users want to exchange geo data with the standard OSM server operated by the OSM community.
Tick the respective checkbox in order to download from and upload to the standard server (see screenshot above). This is the default setting.
Advanced option: Downloading and uploading to a custom server
Some JOSM users need to configure the API URL of an OSM server because they are working with a custom server:
- Some users are working with local installations of the OSM server
- Some users are working with development and test instances of the OSM server (for instance with http://api06.dev.openstreetmap.org).
In order to use a custom URL:
- Remove the tick in the checkbox for the standard API URL (see screenshot above)
- Enter the API URL
Click on Validate to test whether an OSM API server is available at the given URL. If so, JOSM will display the icon to the right of the input field for the API URL. If the URL isn't valid, JOSM will display the icon .
Working anonymously or with an OSM account
You don't need to identify and authenticate yourself provided that you neither upload data to the OSM server nor download data for which you must authenticate first.
If you work anonymously you are allowed
- to download geo-data from the OSM server and save it to a local file
- to download public GPS traces from the OSM server
- to load geo data from a file, edit it, and save it back to a file
However, you can't
- upload geo-data to the OSM server. You can't created, update, or close changesets either.
- download your private GPS traces
Basic authentication is the basic mechanism to authenticate yourself at the OSM server.
Here's a screenshot of the preferences panel for basic authentication:
To use Basic Authentication
- Go to the tab Authentication in the Connection Preferences
- Select the authentication method Basic authentication
- Enter your OSM username and your OSM password
OAuth based authentication
OAuth is an open protocol to allow secure API authorization in a simple and standard method from desktop and web applications. The OSM server supports OAuth in addition to basic authentication.
OAuth has two major advantages over basic authentication:
- Your OSM password doesn't have to be saved in clear text in the JOSM preferences file.
- Your OSM password has to be transferred encrypted only once over the Internet, in contrast to basic authentication where your OSM password is transferred unencrypted as part of every request sent from JOSM to the OSM server.
For advanced users, OAuth has additional advantages:
- With OAuth you can generate restricted Access Tokens which you given somebody else such that another mapper can act on your behalf. For instance, a mapper could generate an Access Token which grants somebody else the right to download its private GPS traces. Even if he gives this Access Token to somebody else, his OSM password is kept private. In addition, he can revoke the special Access Token at any time. JOSM supports this kind of advanced configuration in the OAuth Authorisation Wizard with the authorisation procedure Manual authorization.
To use OAuth based Authentication
- In the Connection Preferences go to the tab Authentication
- Select the authentication method OAuth based authentication
- Click on Authorise now to launch the OAuth Authorisation Wizard (see screenshot below)
This will launch the OAuth Authorisation Wizard. Use one of the available authorization procedures in this dialog to get a valid Access Token.
JOSM displays the retrieved Access Token in the preferences panel (see screenshot below):
Deselect the checkbox Save to preferences if you don't want to save the Access Token in the JOSM preferences. If you don't save it the Access Token will be lost when you close JOSM. If you later startup JOSM again you will have to retrieve a new Access Token to work with OAuth based authentication again.
Click on Test Access Token to submit a test request with the token to the OSM server. JOSM will analyse whether this token is authorized to access the OSM server.
Click on New Access Token to generate a new Access Token.
Advanced OAuth parameters
Select the checkbox Display Advanced OAuth parameters to display the important OAuth parameters
- the Consumer Key and the Consumer Secret identifying JOSM as OAuth consumer
- the Request Token URL where JOSM can retrieve Request Tokens
- the Access Token URL where JOSM can retrieve Access Tokens
- the Authorise URL where JOSM users are redirected to to authorise a Request Token
- Go to the tab Proxy settings in the Connection Preferences
- Select one of the available options and enter additional configuration parameters
- Save the preferences
Using the standard system proxy
If you always want to use the proxy defined as standard proxy on your computer you have to start up JOSM with a special command. The command line has to include the parameter -Djava.net.useSystemProxies=true, for instance
java -Djava.net.useSystemProxies=true -jar josm.jar
Using the manually configured proxy
If there is a need for personal authentication for your proxy, remember to include the NT-domain with your username, e.g. domain\username. This issue is due to proxy implementation in java.net.HttpURLConnection.