Cloud Application Integration (On-Premises) : Integration Server Built-In Services : OAuth Folder : pub.oauth:authorize
pub.oauth:authorize
Initiates an authorization request from a client application to the authorization server.
Input Parameters
response_type
String The grant type preferred by the client. This parameter informs the authorization server how to respond to the client. Set to:
*code for the authorization code grant. When set to code, the response from authorization server must include an OAuth authentication code the client can exchange for an access token.
*token for an implicit grant type. When set to token, the response from authorization server includes an OAuth access token for the client.
For more information about grant types, see Usage Notes.
client_id
String The client identifier generated by the authorization server when the client application is registered. The client_id is used to authenticate the client to the authorization server.
redirect_uri
String Optional. The URI that the authorization server will use to redirect the client when the client is authorized.
This parameter is required if the client is registered with more than one redirect URI. The value for redirect_uri must match one of the client's registered redirect URIs.
scope
String Optional. The name of the scope associated with the client. The scope defines the level of access requested by the client.
Specify the name of one or more scopes. Use a space to separate the name of the scopes. For example:
scope1 scope2 scope3
The scopes you specify must already exist on the authorization server. For information about creating a scope, see webMethods Integration Server Administrator’s Guide.
state
String Optional. A unique string used to maintain the state between the request and callback. When the authorization server redirects the user to the redirect_uri, the value for state will be included in the response. Software AG recommends using this parameter to protect against cross-site request forgery (CSRF) attacks.
Output Parameters
None.
Usage Notes
This service must be invoked using HTTPS unless the Require HTTPS setting on the Security > OAuth > Edit OAuth Global Settings page is disabled.
When you register a client, you must consider the grant type the client should use to obtain an access token. Integration Server supports the following grant types:
*Authorization code. Requires the client to authenticate to the authorization server before obtaining an access token. The authentication code supplied by the authorization server is included in the redirection URI. The client can refresh an expired token. To implement an authorization code grant, set the response_type to code.
*Implicit. Less secure than the authorization code grant. It does not require the client to authenticate to the authorization server. The authentication server includes the access token in the redirection URI. The client cannot refresh an expired token. To implement an implicit grant, set the response_type to token.
Authentication code is not persisted in the cache. If Integration Server is restarted after the authorization code is issued but before the access token is requested, Integration Server will reject the request for the access token.
Copyright © 2015- 2016 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback