Changes between Version 34 and Version 35 of Help/Dialog/OAuthAuthorisationWizard


Ignore:
Timestamp:
2020-07-03T12:48:05+02:00 (5 years ago)
Author:
skyper
Comment:

-> ; link=; https

Legend:

Unmodified
Added
Removed
Modified

  • Help/Dialog/OAuthAuthorisationWizard

    v34 v35  
    44
    55== OAuth in a nutshell ==
    6 [http://oauth.net/ OAuth] is an open protocol to allow secure API authorisation in a simple and standard method from desktop and web applications.
     6[https://oauth.net/ OAuth] is an open protocol to allow secure API authorization in a simple and standard method from desktop and web applications.
    77
    88=== Standard use case - keep your OSM password private ===
    … …  
    1111OAuth has two major advantages over Basic Authentication:
    1212 1. Your OSM password doesn't have to be saved in clear text in the JOSM preferences file.
    13  1. Your OSM password has to be transferred '''only once''' over the Internet on a '''secure connection''', in contrast to basic authentication where your OSM password is transferred as part of every request sent from JOSM to the OSM server in clear text.
     13 1. Your OSM password has to be transferred **only once** over the Internet on a **secure connection**, in contrast to basic authentication where your OSM password is transferred as part of every request sent from JOSM to the OSM server in clear text.
    1414
    1515In OAuth terminology, a JOSM user authorises JOSM to access the OSM server on the user's behalf. During the authorisation process the OSM password never needs to be entered into a JOSM dialog if the user doesn't fully trust JOSM (unless wanting to for convenience reasons [wikitr:/Help/Dialog/OAuthAuthorisationWizard#FullyAutomaticAuthorisation see here]). Rather, the OSM server issues an Access Token which JOSM presents to the OSM server when it uploads data on behalf of the user. Access Tokens don't reveal the user's password and they can be revoked at any time.
    … …  
    2323== The OAuth Authorisation Wizard ==
    2424The Oauth authorisation wizard is located in the preferences under [wikitr:/Help/Preferences/Connection Connection settings].
    25 === What does authentication/authorisation mean? ===
    26 When you upload geodata to the OSM server you have to tell the server who you are. The OSM server will '''identify''' every uploading mapper by asking for an OSM username. The OSM server furthermore needs to '''authenticate''' this identity, i.e. to reliably determine whether the mapper is indeed the claimed user. For this purpose, it asks for a password in addition to the username. The server's assumption is that whoever knows the secret password for username xyz is reliably authenticated to ''be'' xyz. A mapper logged in with an authenticated username and password is entitled to run a broad range of operations on the server. The mapper is '''authorised''' to upload data, to create changesets, to close changesets, to upload GPS traces, to read and changes personal preferences on the server, to invite others as friends, to send emails to other accounts, etc. Currently, it isn't possible to create an OSM account with an OSM username and a password with restricted rights, i.e. an account that would only be able to upload GPS traces, but not map data. Whoever has successfully '''authenticated''' with an OSM username and an OSM password is '''fully authorised''' to do everything an OSM user can normally do on the server.
     25=== What does authentication/authorization mean? ===
     26When you upload geodata to the OSM server you have to tell the server who you are. The OSM server will **identify** every uploading mapper by asking for an OSM username. The OSM server furthermore needs to **authenticate** this identity, i.e. to reliably determine whether the mapper is indeed the claimed user. For this purpose, it asks for a password in addition to the username. The server's assumption is that whoever knows the secret password for username xyz is reliably authenticated to ''be'' xyz. A mapper logged in with an authenticated username and password is entitled to run a broad range of operations on the server. The mapper is ***authorized** to upload data, to create changesets, to close changesets, to upload GPS traces, to read and changes personal preferences on the server, to invite others as friends, to send emails to other accounts, etc. Currently, it isn't possible to create an OSM account with an OSM username and a password with restricted rights, i.e. an account that would only be able to upload GPS traces, but not map data. Whoever has successfully **authenticated** with an OSM username and an OSM password is **fully authorized** to do everything an OSM user can normally do on the server.
    2727
    28 This is where OAuth comes into play: OAuth allows you to '''authorise''' somebody else to act in a restricted way on your behalf. Instead of giving away your OSM username and your OSM password, which would fully entitle the recipient to act on your behalf at the OSM server, you only give away a "ticket" on which the granted rights are listed. This ticket is called an '''Access Token'''. Restrictions applied to an Access Token include:
     28This is where OAuth comes into play: OAuth allows you to **authorize** somebody else to act in a restricted way on your behalf. Instead of giving away your OSM username and your OSM password, which would fully entitle the recipient to act on your behalf at the OSM server, you only give away a "ticket" on which the granted rights are listed. This ticket is called an **Access Token**. Restrictions applied to an Access Token include:
    2929  * an Access Token is only valid for a specific client (called a Consumer in OAuth terminology), i.e. only for JOSM, but not for OpenStreetBugs
    3030  * an Access Token is only valid for specific operations, i.e. only for uploading GPS traces, but not for uploading map data
    … …  
    3333In addition to username/password pairs, the OSM server also accepts OAuth Access Tokens to authenticate and authorise a user. More specifically, it accepts requests ''signed with such a token'', but this is beyond of the scope of this online help.
    3434
    35 The OAuth Authorisation Wizard allows you to receive a valid OAuth Access Token, provided that you have an OSM username and OSM password, or to enter and use an OAuth Access Token in JOSM, provided that you got one from somebody else who has an OSM username and an OSM password.
     35The OAuth Authorization Wizard allows you to receive a valid OAuth Access Token, provided that you have an OSM username and OSM password, or to enter and use an OAuth Access Token in JOSM, provided that you got one from somebody else who has an OSM username and an OSM password.
    3636
    37 === Fully automatic authorisation process ===#FullyAutomaticAuthorisation
     37=== Fully automatic authorization process ===#FullyAutomaticAuthorisation
    3838The easiest way to get an Access Token is to let JOSM fully automatically retrieve one from the OSM server.
    3939
    40 1. '''Step 1/3'''  - Open the preferences dialog
     401. **Step 1/3**  - Open the preferences dialog
    4141
    42     Click on the '''Preferences''' button in the toolbar. In the dialog, select the [wikitr:/Help/Preferences/Connection Connection Setting] tab.
     42    Click on the **Preferences** button in the toolbar. In the dialog, select the [wikitr:/Help/Preferences/Connection Connection Setting] tab.
    4343
    44 2. '''Step 2/3'''  - Get the Access Token
     442. **Step 2/3**  - Get the Access Token
    4545
    46  Enter your OSM username and your OSM password and click on '''Authorise now'''.
     46 Enter your OSM username and your OSM password and click on **Authorize now**.
    4747   
    48  [[Image(fully-authomatic-1.png)]]
     48 [[Image(fully-authomatic-1.png,link=)]]
    4949
    50 3. '''Step 3/3''' - Accept the Access Token
     503. **Step 3/3**' - Accept the Access Token
    5151
    5252 JOSM displays the retrieved Access Token.
    5353   
    54  [[Image(fully-authomatic-2.png)]]
     54 [[Image(fully-authomatic-2.png,link=)]]
    5555
    5656* 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.
    5757* Click on ''Test Access Token" to test the token
    58 * Click on '''Accept Access Token''' to accept it.
     58* Click on **Accept Access Token** to accept it.
    5959
    6060==== Restricting the granted privileges ====
    61 When JOSM fully-automatically requests and authorises an Access Token, it grants it five privileges:
     61When JOSM fully-automatically requests and authorizes an Access Token, it grants it five privileges:
    6262* the right to upload data to the OSM server
    6363* the right to upload GPS traces to the OSM server
    … …  
    6868These are the default settings. If you want to restrict the granted privileges:
    6969
    70 1. Click the tab '''Granted rights'''
     701. Click the tab **Granted rights**
    71711. Deselect each privilege which should not be granted to the requested Access Token
    7272
    73 [[Image(fully-authomatic-privileges.png)]]
     73[[Image(fully-authomatic-privileges.png,link=)]]
    7474
    7575==== Advanced OAuth parameters ==== #FullyAutomaticAdvanced
    … …  
    8080In order to edit the Advanced OAuth parameters
    8181
    82  1. Click the tab '''Advanced OAuth parameters'''
    83  1. Deselect the checkbox '''Use default settings'''
     82 1. Click the tab **Advanced OAuth parameters**
     83 1. Deselect the checkbox **Use default settings**
    8484 1. Enter your values for the five OAuth parameters
    8585
    86 [[Image(fully-automatic-advanced.png)]]
     86[[Image(fully-automatic-advanced.png,link=)]]
    8787
    88 === Semi-automatic authorisation process ===#Semi-automaticauthorisationprocess
    89 You can also retrieve an Access Token semi-automatically. If you use this process you have to use both dialogs in JOSM and the OSM website launched in an external browser to create and authorise the Access Token. In contrast to the fully automatic process you never have to enter your OSM username or your OSM password into a JOSM dialog. This process is therefore suitable for a user which - for whatever reason - never wants to use their OSM password outside of the secure login page of the OSM website. The fully automatic process runs exactly the same steps that would run manually in the semi-automatic process, just without your intervention.
     88=== Semi-automatic authorization process ===#Semi-automaticauthorisationprocess
     89You can also retrieve an Access Token semi-automatically. If you use this process you have to use both dialogs in JOSM and the OSM website launched in an external browser to create and authorize the Access Token. In contrast to the fully automatic process you never have to enter your OSM username or your OSM password into a JOSM dialog. This process is therefore suitable for a user which - for whatever reason - never wants to use their OSM password outside of the secure login page of the OSM website. The fully automatic process runs exactly the same steps that would run manually in the semi-automatic process, just without your intervention.
    9090
     911. **Step 1/3** - Get the Request Token
    9192
    92 1. '''Step 1/3''' - Get the Request Token
     93 Click on **Retrieve Request Token** to retrieve an OAuth Request Token.
     94   
     95 [[Image(semi-automatic-step-1.png,link=)]]
    9396
    94  Click on '''Retrieve Request Token''' to retrieve an OAuth Request Token.
     972. **Step 2/3** - Authorise the Request Token in an external browser
     98
     99 JOSM now launches an external browser with the OSM website. Please login and follow the instructions. Then switch back to the OAuth Authorization Wizard and click on **Retrieve Access Token**.
    95100   
    96  [[Image(semi-automatic-step-1.png)]]
     101 [[Image(semi-automatic-step-2.png,link=)]]
    97102
    98 2. '''Step 2/3''' - Authorise the Request Token in an external browser
     1033. **Step 3/3** - Accept the Access Token
    99104
    100  JOSM now launches an external browser with the OSM website. Please login and follow the instructions. Then switch back to the OAuth Authorisation Wizard and click on '''Retrieve Access Token'''.
     105 JOSM displays the retrieved Access Token. Click on '**Accept Access Token** to accept it.
    101106   
    102  [[Image(semi-automatic-step-2.png)]]
    103 
    104 3. '''Step 3/3''' - Accept the Access Token
    105 
    106  JOSM displays the retrieved Access Token. Click on '''Accept Access Token''' to accept it.
    107    
    108  [[Image(semi-automatic-step-3.png)]]
     107 [[Image(semi-automatic-step-3.png,link=)]]
    109108
    110109
    111110==== Advanced OAuth parameters ==== #AdvancedOAuthparameters
    112 When JOSM semi-automatically requests and authorises an Access Token, it uses default values for the OAuth parameters. Advanced users may want to change these parameters
     111When JOSM semi-automatically requests and authorizes an Access Token, it uses default values for the OAuth parameters. Advanced users may want to change these parameters
    113112* in order to use a different Consumer Token (consisting of a Consumer Key and a Consumer Secret). This allows you to create your own Consumer Token for JOSM and then use it in JOSM.
    114113* in order to use it on a different than the standard OSM server. For instance, this allows users to use OAuth with an OSM development server or with a local installation of the OSM server application.
    … …  
    116115In order to edit the Advanced OAuth parameters
    117116
    118  1. Select the checkbox '''Display Advanced OAuth Parameters'''
    119  1. Enter your values for the five OAuth parameters
     1171. Select the checkbox **Display Advanced OAuth Parameters**
     1181. Enter your values for the five OAuth parameters
    120119
    121 [[Image(semi-automatic-advanced.png)]]
     120[[Image(semi-automatic-advanced.png,link=)]]
    122121
    123 === Manual authorisation process ===
    124 The manual authorisation process allows you to enter an arbitrary Access Token. You can use this process
     122=== Manual authorization process ===
     123The manual authorization process allows you to enter an arbitrary Access Token. You can use this process
    125124
    126125* to enter an Access Token you have kept in a secure place, for instance in a secure store for credentials
    127126* to enter an Access Token you have received from somebody else, for instance from another mapper who granted you restricted account access
    128127
    129 1. '''Step 1/1'''  - Enter the Access Token and accept it
     1281. **Step 1/1**  - Enter the Access Token and accept it
    130129
    131  Enter the Access Token and click on '''Accept Access Token'''.
     130 Enter the Access Token and click on **Accept Access Token**.
    132131
    133  [[Image(manual.png)]]
     132 [[Image(manual.png,link=)]]
    134133 
    135134
    … …  
    138137
    139138== Troubleshooting ==
    140 * If you are working on a university or corporate network, a firewall may prevent the OAuth authentification request. \\
     139* If you are working on a university or corporate network, a firewall may prevent the OAuth authentication request. \\
    141140 Please check the corresponding connection with your network engineer.
    142141----