JetBrains Space EAP Help

Resource Owner Password Credentials Flow

This flow can be used for a client that accesses resources on behalf of a user (resource owner) which credentials the client knows. The client can be, for example, a device operating system or a highly privileged application.

The client should be capable of obtaining the resource owner's credentials — username and password, typically via an interactive form.

The client should be registered with Space as Service Account or Mobile or Desktop App.


The client should make a request to the token endpoint <Space service URL>/oauth/token by adding the following parameters to the entity-body of HTTP request in the application/x-www-form-urlencoded format with UTF-8 character encoding:

To obtain an access token from Space, your client needs to provide values for the following parameters in authorization requests:

grant_typeRequired. Specifies the grant type in an OAuth 2.0 request. Set value to password.
usernameRequired. The resource owner username.
passwordRequired. The resource owner password.
client_secretThe private identifier assigned to your client application when you register it in Space. To get the client secret, go to administration.png Administration → Applications and choose your client from the list.

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):


Wildcards are accepted. For global rights, category is omitted.


AddNewProfile,AddNewTeam Team:EditTeam Profile:EditAbsences,EditLanguages Project:*

The rights you specify in scope should be first added to the list of requested rights and authorized for your client in Space.

access_typeIndicates 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 offline value. 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_id and client_secret in a single string using semicolon as a delimiter and encode it into Base64 format.

For example, the client makes the following HTTP request using transport-layer security:

POST /oauth/token Host: Authorization: Basic dmFsaWQtc2VydmljZS1pZDp2YWxpZC1zZXJ2aWNlLXNlY3JldA== Content-Type: application/x-www-form-urlencoded grant_type=client_credentials&scope=**

If the request is valid, Space will authenticate the client.


If the access token request is valid and authorized, the Space server issues an access token and refresh token.


HTTP/1.1 200 OK Content-Type: application/json;charset=UTF-8 Cache-Control: no-store Pragma: no-cache { "token_type": "Bearer", "expires_in": 600, "access_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIzNThlMDRlOS1jNDc1LTRkNGUtOGM4OS1lODA3ZTQxNjk3MmMiLCJhdWQiOiIzNThlMDRlOS1jNDc1LTRkNGUtOGM4OS1lODA3ZTQxNjk3MmMiLCJvcmdEb21haW4iOiJqZXRicmFpbnMudGVhbSIsInNjb3BlIjoiKioiLCJuYW1lIjoiTXkgU2VydmljZSIsImlzcyI6Imh0dHBzOi8vamV0YnJhaW5zLnRlYW0iLCJwcmluY2lwYWxfdHlwZSI6IlNFUlZJQ0UiLCJleHAiOjE1NjQ1MDU0MzAsImlhdCI6MTU2NDUwNDgzMH0._1uLmGWUfeG52p4_LcLdZN29at14CGG_RE4KusWY34A", "refresh_token": null, "scope": "**" }


If the request failed client 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 client, or is otherwise malformed.

  • invalid_client— Client authentication failed (e.g., unknown client, no client 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 client 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 client.

  • 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 client.

  • unauthorized_client— The authenticated client 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 client 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.


HTTP/1.1 400 Bad Request Content-Type: application/json;charset=UTF-8 Cache-Control: no-store Pragma: no-cache { "error":"invalid_request" }
Last modified: 18 November 2020