Resource Owner Password Credentials Flow
We do not recommend that you use Resource Owner Password Credentials Flow as it is potentially less secure comparing to other flows.
This flow can be used for an application that accesses resources on behalf of a user (resource owner) which credentials the application knows. The application can be, for example, a device operating system or a highly privileged application.
Typically, the application obtains the user's Space credentials – username and password, via an interactive form. The application then uses these credentials to get full access to Space on behalf of the user.
You don't have to explicitly enable the flow for an application during the registration– the flow is enabled by default.
For more details on the flow, refer to Resource owner password credentials flow specification.
To obtain an access token from Space, the application should make a request to the token endpoint
<Space service URL>/oauth/token.
Add the following parameters to the HTTP header of the request:
Required. The ID assigned to your client application when you register it in Space. To get the client ID, go toand choose your application from the list.
Required. The private identifier assigned to your client application when you register it in Space. To get the client secret, go toand choose your application from the list.
Add the following parameters to the entity-body of the HTTP request in the
application/x-www-form-urlencoded format with UTF-8 character encoding:
Required. Specifies the grant type in an OAuth 2.0 request. Set value to
Required. The resource owner username.
Required. The resource owner password.
Required. A space separated list of rights required to access specific resources in Space.
The rights are grouped in four categories: Global, Profile, Team, Project. Use the following syntax to specify the rights (shown here in BNF notation):<SCOPE> ::= <ALL> | <TOKEN_LIST> <ALL> ::= '**' <TOKEN_LIST> ::= <TOKEN> (' ' <TOKEN>)* <TOKEN> ::= <GLOBAL_PERMISSIONS_TOKEN> | <ENTITY_PERMISSIONS_TOKEN> <GLOBAL_PERMISSIONS_TOKEN> ::= <PERMISSIONS> <ENTITY_PERMISSIONS_TOKEN> ::= <ENTITY> ':' <PERMISSIONS> <ENTITY> ::= 'Team' | 'Project' | 'Profile' | 'etc.' <PERMISSIONS> ::= <ALL_PERMISSIONS> | <PERMISSION_LIST> <ALL_PERMISSIONS> ::= '*' <PERMISSION_LIST> ::= <PERMISSION> (',' <PERMISSION>)*
Wildcards are accepted. For global rights, category is omitted.
Example:AddNewProfile,AddNewTeam Team:EditTeam Profile:EditAbsences,EditLanguages Project:*
The rights you specify in
scopeshould be first added to the list of requested rights and authorized for your application in Space.
Indicates whether the application requires access to Space when the user is not online. Allowed values:
online(used by default) and
offline. If the application requires refreshing access tokens when the user is not online, use the
offlinevalue. In this case Space issues a refresh token for the application the first time it exchanges an authorization code for a user. Refer to the Refresh Token page for more information.
The request must contain the "Authorization" header in the following format:
Authorization: Basic <base64(client_id + “:” + client_secret)>
To get a correct value, combine the
client_secret in a single string using semicolon as a delimiter and encode it into Base64 format.
For example, the application makes the following HTTP request using transport-layer security:
If the request is valid, Space will authenticate the application.
If the access token request is valid and authorized, the Space server issues an access token and refresh token.
If the request failed application authentication or is invalid, Space responds with an HTTP 400 (Bad Request) status code (unless specified otherwise) and includes the following parameters with the response:
A single ASCII [USASCII] error code from the following:
invalid_request— The request is missing a required parameter, includes an unsupported parameter value (other than grant type), repeats a parameter, includes multiple credentials, utilizes more than one mechanism for authenticating the application, or is otherwise malformed.
invalid_client— Application authentication failed (e.g., unknown application, no application authentication included, or unsupported authentication method). The authorization server may return an HTTP 401 (Unauthorized) status code to indicate which HTTP authentication schemes are supported. If the application attempted to authenticate via the "Authorization" request header field, the Space server will respond with an HTTP 401 (Unauthorized) status code and include the "WWW-Authenticate" response header field matching the authentication scheme used by the application.
invalid_grant— The provided authorization grant (e.g., authorization code, resource owner credentials) or refresh token is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another application.
unauthorized_client— The authenticated application is not authorized to use this authorization grant type.
unsupported_grant_type— The authorization grant type is not supported by Space.
invalid_scope— The requested scope is invalid, unknown, malformed, or exceeds the scope granted by the resource owner.
Human-readable ASCII [USASCII] text providing additional information, used to assist the application developer in understanding the error that occurred.
The parameters are included in the entity-body of the HTTP response using the "application/json" media type. The parameters are serialized into a JSON structure by adding each parameter at the highest structure level. Parameter names and string values are included as JSON strings. Numerical values are included as JSON numbers. The order of parameters does not matter and can vary.