text
stringlengths 65
20k
|
|---|
2-1Grant Type About the Grant Type Use Cases and Risks Resource owner password credential (ROPC)The resource owner's password credentials (that is, the user name and password) can be used by the OAuth client directly as an authorization grant to obtain an access token.The resource owner password credentials grant type is suitable for cases where the resource owner has a trust relationship with the OAuth client.When using the resource owner password credentials grant, the user provides the credentials (user name and password) directly to the application.The application then uses the credentials to obtain an access token from the OAuth token service.The resource owner password credentials grant is a grant workflow where the client application, together with its client identifier and secret, sends the user name and password in exchange for an access token.Instead of the user having to log in and approve the authorization request in a web interface, the user can enter the user name and password in the client application user interface directly.This workflow has different security properties than other OAuth workflows.The primary difference is that the user's password is accessible to the application.This requires a strong trust of the application by the user.The resource owner password credentials grant has the following characteristics: The client is required to have knowledge of user credentials.Is not a browser-based end user interaction.A refresh token is allowed.An access token is in the context of the end user.This grant can be used by applications that want to programmatically invoke the integration without any user intervention.Use this grant only with trusted first-party clients that securely handle user credentials.Even though this grant type can be used by client applications to acquire an OAuth access token to use for sending the request to invoke an integration in a programmatic manner, Oracle Integration does not recommend the resource owner password credential grant because of the following risks: Risks This grant type carries a higher risk than other grant types because it maintains the password anti-pattern this protocol seeks to avoid. |
The resource owner password credentials grant type is suitable for cases where the resource owner has a trust relationship with the OAuth client.When using the resource owner password credentials grant, the user provides the credentials (user name and password) directly to the application.The application then uses the credentials to obtain an access token from the OAuth token service.The resource owner password credentials grant is a grant workflow where the client application, together with its client identifier and secret, sends the user name and password in exchange for an access token.Instead of the user having to log in and approve the authorization request in a web interface, the user can enter the user name and password in the client application user interface directly.This workflow has different security properties than other OAuth workflows.The primary difference is that the user's password is accessible to the application.This requires a strong trust of the application by the user.The resource owner password credentials grant has the following characteristics: The client is required to have knowledge of user credentials.Is not a browser-based end user interaction.A refresh token is allowed.An access token is in the context of the end user.This grant can be used by applications that want to programmatically invoke the integration without any user intervention.Use this grant only with trusted first-party clients that securely handle user credentials.Even though this grant type can be used by client applications to acquire an OAuth access token to use for sending the request to invoke an integration in a programmatic manner, Oracle Integration does not recommend the resource owner password credential grant because of the following risks: Risks This grant type carries a higher risk than other grant types because it maintains the password anti-pattern this protocol seeks to avoid.The client can abuse the password or the password can unintentionally be disclosed to an attacker (for example, through log files or other records kept by the client). |
When using the resource owner password credentials grant, the user provides the credentials (user name and password) directly to the application.The application then uses the credentials to obtain an access token from the OAuth token service.The resource owner password credentials grant is a grant workflow where the client application, together with its client identifier and secret, sends the user name and password in exchange for an access token.Instead of the user having to log in and approve the authorization request in a web interface, the user can enter the user name and password in the client application user interface directly.This workflow has different security properties than other OAuth workflows.The primary difference is that the user's password is accessible to the application.This requires a strong trust of the application by the user.The resource owner password credentials grant has the following characteristics: The client is required to have knowledge of user credentials.Is not a browser-based end user interaction.A refresh token is allowed.An access token is in the context of the end user.This grant can be used by applications that want to programmatically invoke the integration without any user intervention.Use this grant only with trusted first-party clients that securely handle user credentials.Even though this grant type can be used by client applications to acquire an OAuth access token to use for sending the request to invoke an integration in a programmatic manner, Oracle Integration does not recommend the resource owner password credential grant because of the following risks: Risks This grant type carries a higher risk than other grant types because it maintains the password anti-pattern this protocol seeks to avoid.The client can abuse the password or the password can unintentionally be disclosed to an attacker (for example, through log files or other records kept by the client).The application can request a scope with complete access to user resources once it possesses the password credential. |
The application then uses the credentials to obtain an access token from the OAuth token service.The resource owner password credentials grant is a grant workflow where the client application, together with its client identifier and secret, sends the user name and password in exchange for an access token.Instead of the user having to log in and approve the authorization request in a web interface, the user can enter the user name and password in the client application user interface directly.This workflow has different security properties than other OAuth workflows.The primary difference is that the user's password is accessible to the application.This requires a strong trust of the application by the user.The resource owner password credentials grant has the following characteristics: The client is required to have knowledge of user credentials.Is not a browser-based end user interaction.A refresh token is allowed.An access token is in the context of the end user.This grant can be used by applications that want to programmatically invoke the integration without any user intervention.Use this grant only with trusted first-party clients that securely handle user credentials.Even though this grant type can be used by client applications to acquire an OAuth access token to use for sending the request to invoke an integration in a programmatic manner, Oracle Integration does not recommend the resource owner password credential grant because of the following risks: Risks This grant type carries a higher risk than other grant types because it maintains the password anti-pattern this protocol seeks to avoid.The client can abuse the password or the password can unintentionally be disclosed to an attacker (for example, through log files or other records kept by the client).The application can request a scope with complete access to user resources once it possesses the password credential.Passwords expire. |
The resource owner password credentials grant is a grant workflow where the client application, together with its client identifier and secret, sends the user name and password in exchange for an access token.Instead of the user having to log in and approve the authorization request in a web interface, the user can enter the user name and password in the client application user interface directly.This workflow has different security properties than other OAuth workflows.The primary difference is that the user's password is accessible to the application.This requires a strong trust of the application by the user.The resource owner password credentials grant has the following characteristics: The client is required to have knowledge of user credentials.Is not a browser-based end user interaction.A refresh token is allowed.An access token is in the context of the end user.This grant can be used by applications that want to programmatically invoke the integration without any user intervention.Use this grant only with trusted first-party clients that securely handle user credentials.Even though this grant type can be used by client applications to acquire an OAuth access token to use for sending the request to invoke an integration in a programmatic manner, Oracle Integration does not recommend the resource owner password credential grant because of the following risks: Risks This grant type carries a higher risk than other grant types because it maintains the password anti-pattern this protocol seeks to avoid.The client can abuse the password or the password can unintentionally be disclosed to an attacker (for example, through log files or other records kept by the client).The application can request a scope with complete access to user resources once it possesses the password credential.Passwords expire.Usage See Prerequisites for Resource Owner Password Credentials .Chapter 2 Authentication Support 2-2Grant Type About the Grant Type Use Cases and Risks In this OAuth flow: The user clicks a link in the client application requesting access to protected resources. |
Instead of the user having to log in and approve the authorization request in a web interface, the user can enter the user name and password in the client application user interface directly.This workflow has different security properties than other OAuth workflows.The primary difference is that the user's password is accessible to the application.This requires a strong trust of the application by the user.The resource owner password credentials grant has the following characteristics: The client is required to have knowledge of user credentials.Is not a browser-based end user interaction.A refresh token is allowed.An access token is in the context of the end user.This grant can be used by applications that want to programmatically invoke the integration without any user intervention.Use this grant only with trusted first-party clients that securely handle user credentials.Even though this grant type can be used by client applications to acquire an OAuth access token to use for sending the request to invoke an integration in a programmatic manner, Oracle Integration does not recommend the resource owner password credential grant because of the following risks: Risks This grant type carries a higher risk than other grant types because it maintains the password anti-pattern this protocol seeks to avoid.The client can abuse the password or the password can unintentionally be disclosed to an attacker (for example, through log files or other records kept by the client).The application can request a scope with complete access to user resources once it possesses the password credential.Passwords expire.Usage See Prerequisites for Resource Owner Password Credentials .Chapter 2 Authentication Support 2-2Grant Type About the Grant Type Use Cases and Risks In this OAuth flow: The user clicks a link in the client application requesting access to protected resources.The client application requests the resource owners user name and password. |
This workflow has different security properties than other OAuth workflows.The primary difference is that the user's password is accessible to the application.This requires a strong trust of the application by the user.The resource owner password credentials grant has the following characteristics: The client is required to have knowledge of user credentials.Is not a browser-based end user interaction.A refresh token is allowed.An access token is in the context of the end user.This grant can be used by applications that want to programmatically invoke the integration without any user intervention.Use this grant only with trusted first-party clients that securely handle user credentials.Even though this grant type can be used by client applications to acquire an OAuth access token to use for sending the request to invoke an integration in a programmatic manner, Oracle Integration does not recommend the resource owner password credential grant because of the following risks: Risks This grant type carries a higher risk than other grant types because it maintains the password anti-pattern this protocol seeks to avoid.The client can abuse the password or the password can unintentionally be disclosed to an attacker (for example, through log files or other records kept by the client).The application can request a scope with complete access to user resources once it possesses the password credential.Passwords expire.Usage See Prerequisites for Resource Owner Password Credentials .Chapter 2 Authentication Support 2-2Grant Type About the Grant Type Use Cases and Risks In this OAuth flow: The user clicks a link in the client application requesting access to protected resources.The client application requests the resource owners user name and password.The user logs in with their user name and password. |
The primary difference is that the user's password is accessible to the application.This requires a strong trust of the application by the user.The resource owner password credentials grant has the following characteristics: The client is required to have knowledge of user credentials.Is not a browser-based end user interaction.A refresh token is allowed.An access token is in the context of the end user.This grant can be used by applications that want to programmatically invoke the integration without any user intervention.Use this grant only with trusted first-party clients that securely handle user credentials.Even though this grant type can be used by client applications to acquire an OAuth access token to use for sending the request to invoke an integration in a programmatic manner, Oracle Integration does not recommend the resource owner password credential grant because of the following risks: Risks This grant type carries a higher risk than other grant types because it maintains the password anti-pattern this protocol seeks to avoid.The client can abuse the password or the password can unintentionally be disclosed to an attacker (for example, through log files or other records kept by the client).The application can request a scope with complete access to user resources once it possesses the password credential.Passwords expire.Usage See Prerequisites for Resource Owner Password Credentials .Chapter 2 Authentication Support 2-2Grant Type About the Grant Type Use Cases and Risks In this OAuth flow: The user clicks a link in the client application requesting access to protected resources.The client application requests the resource owners user name and password.The user logs in with their user name and password.The client application exchanges those credentials for an access token, and often a refresh token, from the Oracle Identity Cloud Service authorization server. |
This requires a strong trust of the application by the user.The resource owner password credentials grant has the following characteristics: The client is required to have knowledge of user credentials.Is not a browser-based end user interaction.A refresh token is allowed.An access token is in the context of the end user.This grant can be used by applications that want to programmatically invoke the integration without any user intervention.Use this grant only with trusted first-party clients that securely handle user credentials.Even though this grant type can be used by client applications to acquire an OAuth access token to use for sending the request to invoke an integration in a programmatic manner, Oracle Integration does not recommend the resource owner password credential grant because of the following risks: Risks This grant type carries a higher risk than other grant types because it maintains the password anti-pattern this protocol seeks to avoid.The client can abuse the password or the password can unintentionally be disclosed to an attacker (for example, through log files or other records kept by the client).The application can request a scope with complete access to user resources once it possesses the password credential.Passwords expire.Usage See Prerequisites for Resource Owner Password Credentials .Chapter 2 Authentication Support 2-2Grant Type About the Grant Type Use Cases and Risks In this OAuth flow: The user clicks a link in the client application requesting access to protected resources.The client application requests the resource owners user name and password.The user logs in with their user name and password.The client application exchanges those credentials for an access token, and often a refresh token, from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server returns the access token to the client application. |
The resource owner password credentials grant has the following characteristics: The client is required to have knowledge of user credentials.Is not a browser-based end user interaction.A refresh token is allowed.An access token is in the context of the end user.This grant can be used by applications that want to programmatically invoke the integration without any user intervention.Use this grant only with trusted first-party clients that securely handle user credentials.Even though this grant type can be used by client applications to acquire an OAuth access token to use for sending the request to invoke an integration in a programmatic manner, Oracle Integration does not recommend the resource owner password credential grant because of the following risks: Risks This grant type carries a higher risk than other grant types because it maintains the password anti-pattern this protocol seeks to avoid.The client can abuse the password or the password can unintentionally be disclosed to an attacker (for example, through log files or other records kept by the client).The application can request a scope with complete access to user resources once it possesses the password credential.Passwords expire.Usage See Prerequisites for Resource Owner Password Credentials .Chapter 2 Authentication Support 2-2Grant Type About the Grant Type Use Cases and Risks In this OAuth flow: The user clicks a link in the client application requesting access to protected resources.The client application requests the resource owners user name and password.The user logs in with their user name and password.The client application exchanges those credentials for an access token, and often a refresh token, from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server returns the access token to the client application.The client application uses the access token in an API call to invoke the integration.Chapter 2 Authentication Support 2-3Grant Type About the Grant Type Use Cases and Risks Client credentials The client credentials grant is used when the OAuth client itself owns the data and doesn't need delegated access from a resource owner. |
Is not a browser-based end user interaction.A refresh token is allowed.An access token is in the context of the end user.This grant can be used by applications that want to programmatically invoke the integration without any user intervention.Use this grant only with trusted first-party clients that securely handle user credentials.Even though this grant type can be used by client applications to acquire an OAuth access token to use for sending the request to invoke an integration in a programmatic manner, Oracle Integration does not recommend the resource owner password credential grant because of the following risks: Risks This grant type carries a higher risk than other grant types because it maintains the password anti-pattern this protocol seeks to avoid.The client can abuse the password or the password can unintentionally be disclosed to an attacker (for example, through log files or other records kept by the client).The application can request a scope with complete access to user resources once it possesses the password credential.Passwords expire.Usage See Prerequisites for Resource Owner Password Credentials .Chapter 2 Authentication Support 2-2Grant Type About the Grant Type Use Cases and Risks In this OAuth flow: The user clicks a link in the client application requesting access to protected resources.The client application requests the resource owners user name and password.The user logs in with their user name and password.The client application exchanges those credentials for an access token, and often a refresh token, from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server returns the access token to the client application.The client application uses the access token in an API call to invoke the integration.Chapter 2 Authentication Support 2-3Grant Type About the Grant Type Use Cases and Risks Client credentials The client credentials grant is used when the OAuth client itself owns the data and doesn't need delegated access from a resource owner.The client credentials grant provides a specific grant flow in which the resource owner (that is, the user) is not involved. |
A refresh token is allowed.An access token is in the context of the end user.This grant can be used by applications that want to programmatically invoke the integration without any user intervention.Use this grant only with trusted first-party clients that securely handle user credentials.Even though this grant type can be used by client applications to acquire an OAuth access token to use for sending the request to invoke an integration in a programmatic manner, Oracle Integration does not recommend the resource owner password credential grant because of the following risks: Risks This grant type carries a higher risk than other grant types because it maintains the password anti-pattern this protocol seeks to avoid.The client can abuse the password or the password can unintentionally be disclosed to an attacker (for example, through log files or other records kept by the client).The application can request a scope with complete access to user resources once it possesses the password credential.Passwords expire.Usage See Prerequisites for Resource Owner Password Credentials .Chapter 2 Authentication Support 2-2Grant Type About the Grant Type Use Cases and Risks In this OAuth flow: The user clicks a link in the client application requesting access to protected resources.The client application requests the resource owners user name and password.The user logs in with their user name and password.The client application exchanges those credentials for an access token, and often a refresh token, from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server returns the access token to the client application.The client application uses the access token in an API call to invoke the integration.Chapter 2 Authentication Support 2-3Grant Type About the Grant Type Use Cases and Risks Client credentials The client credentials grant is used when the OAuth client itself owns the data and doesn't need delegated access from a resource owner.The client credentials grant provides a specific grant flow in which the resource owner (that is, the user) is not involved.When using this grant, the client application requests an access token only with its own credentials (the identifier and secret) or an assertion from the token endpoint and uses the access token on behalf of the client application itself. |
An access token is in the context of the end user.This grant can be used by applications that want to programmatically invoke the integration without any user intervention.Use this grant only with trusted first-party clients that securely handle user credentials.Even though this grant type can be used by client applications to acquire an OAuth access token to use for sending the request to invoke an integration in a programmatic manner, Oracle Integration does not recommend the resource owner password credential grant because of the following risks: Risks This grant type carries a higher risk than other grant types because it maintains the password anti-pattern this protocol seeks to avoid.The client can abuse the password or the password can unintentionally be disclosed to an attacker (for example, through log files or other records kept by the client).The application can request a scope with complete access to user resources once it possesses the password credential.Passwords expire.Usage See Prerequisites for Resource Owner Password Credentials .Chapter 2 Authentication Support 2-2Grant Type About the Grant Type Use Cases and Risks In this OAuth flow: The user clicks a link in the client application requesting access to protected resources.The client application requests the resource owners user name and password.The user logs in with their user name and password.The client application exchanges those credentials for an access token, and often a refresh token, from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server returns the access token to the client application.The client application uses the access token in an API call to invoke the integration.Chapter 2 Authentication Support 2-3Grant Type About the Grant Type Use Cases and Risks Client credentials The client credentials grant is used when the OAuth client itself owns the data and doesn't need delegated access from a resource owner.The client credentials grant provides a specific grant flow in which the resource owner (that is, the user) is not involved.When using this grant, the client application requests an access token only with its own credentials (the identifier and secret) or an assertion from the token endpoint and uses the access token on behalf of the client application itself.The token endpoint does not issue a refresh token. |
Use this grant only with trusted first-party clients that securely handle user credentials.Even though this grant type can be used by client applications to acquire an OAuth access token to use for sending the request to invoke an integration in a programmatic manner, Oracle Integration does not recommend the resource owner password credential grant because of the following risks: Risks This grant type carries a higher risk than other grant types because it maintains the password anti-pattern this protocol seeks to avoid.The client can abuse the password or the password can unintentionally be disclosed to an attacker (for example, through log files or other records kept by the client).The application can request a scope with complete access to user resources once it possesses the password credential.Passwords expire.Usage See Prerequisites for Resource Owner Password Credentials .Chapter 2 Authentication Support 2-2Grant Type About the Grant Type Use Cases and Risks In this OAuth flow: The user clicks a link in the client application requesting access to protected resources.The client application requests the resource owners user name and password.The user logs in with their user name and password.The client application exchanges those credentials for an access token, and often a refresh token, from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server returns the access token to the client application.The client application uses the access token in an API call to invoke the integration.Chapter 2 Authentication Support 2-3Grant Type About the Grant Type Use Cases and Risks Client credentials The client credentials grant is used when the OAuth client itself owns the data and doesn't need delegated access from a resource owner.The client credentials grant provides a specific grant flow in which the resource owner (that is, the user) is not involved.When using this grant, the client application requests an access token only with its own credentials (the identifier and secret) or an assertion from the token endpoint and uses the access token on behalf of the client application itself.The token endpoint does not issue a refresh token.This is because refresh tokens are not supported by the client credentials grant. |
Even though this grant type can be used by client applications to acquire an OAuth access token to use for sending the request to invoke an integration in a programmatic manner, Oracle Integration does not recommend the resource owner password credential grant because of the following risks: Risks This grant type carries a higher risk than other grant types because it maintains the password anti-pattern this protocol seeks to avoid.The client can abuse the password or the password can unintentionally be disclosed to an attacker (for example, through log files or other records kept by the client).The application can request a scope with complete access to user resources once it possesses the password credential.Passwords expire.Usage See Prerequisites for Resource Owner Password Credentials .Chapter 2 Authentication Support 2-2Grant Type About the Grant Type Use Cases and Risks In this OAuth flow: The user clicks a link in the client application requesting access to protected resources.The client application requests the resource owners user name and password.The user logs in with their user name and password.The client application exchanges those credentials for an access token, and often a refresh token, from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server returns the access token to the client application.The client application uses the access token in an API call to invoke the integration.Chapter 2 Authentication Support 2-3Grant Type About the Grant Type Use Cases and Risks Client credentials The client credentials grant is used when the OAuth client itself owns the data and doesn't need delegated access from a resource owner.The client credentials grant provides a specific grant flow in which the resource owner (that is, the user) is not involved.When using this grant, the client application requests an access token only with its own credentials (the identifier and secret) or an assertion from the token endpoint and uses the access token on behalf of the client application itself.The token endpoint does not issue a refresh token.This is because refresh tokens are not supported by the client credentials grant.When the access token expires, the client application must request a new access token. |
The client can abuse the password or the password can unintentionally be disclosed to an attacker (for example, through log files or other records kept by the client).The application can request a scope with complete access to user resources once it possesses the password credential.Passwords expire.Usage See Prerequisites for Resource Owner Password Credentials .Chapter 2 Authentication Support 2-2Grant Type About the Grant Type Use Cases and Risks In this OAuth flow: The user clicks a link in the client application requesting access to protected resources.The client application requests the resource owners user name and password.The user logs in with their user name and password.The client application exchanges those credentials for an access token, and often a refresh token, from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server returns the access token to the client application.The client application uses the access token in an API call to invoke the integration.Chapter 2 Authentication Support 2-3Grant Type About the Grant Type Use Cases and Risks Client credentials The client credentials grant is used when the OAuth client itself owns the data and doesn't need delegated access from a resource owner.The client credentials grant provides a specific grant flow in which the resource owner (that is, the user) is not involved.When using this grant, the client application requests an access token only with its own credentials (the identifier and secret) or an assertion from the token endpoint and uses the access token on behalf of the client application itself.The token endpoint does not issue a refresh token.This is because refresh tokens are not supported by the client credentials grant.When the access token expires, the client application must request a new access token.Client credentials have the following characteristics: Are used by confidential OAuth clients. |
The application can request a scope with complete access to user resources once it possesses the password credential.Passwords expire.Usage See Prerequisites for Resource Owner Password Credentials .Chapter 2 Authentication Support 2-2Grant Type About the Grant Type Use Cases and Risks In this OAuth flow: The user clicks a link in the client application requesting access to protected resources.The client application requests the resource owners user name and password.The user logs in with their user name and password.The client application exchanges those credentials for an access token, and often a refresh token, from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server returns the access token to the client application.The client application uses the access token in an API call to invoke the integration.Chapter 2 Authentication Support 2-3Grant Type About the Grant Type Use Cases and Risks Client credentials The client credentials grant is used when the OAuth client itself owns the data and doesn't need delegated access from a resource owner.The client credentials grant provides a specific grant flow in which the resource owner (that is, the user) is not involved.When using this grant, the client application requests an access token only with its own credentials (the identifier and secret) or an assertion from the token endpoint and uses the access token on behalf of the client application itself.The token endpoint does not issue a refresh token.This is because refresh tokens are not supported by the client credentials grant.When the access token expires, the client application must request a new access token.Client credentials have the following characteristics: Are used by confidential OAuth clients.The OAuth client application communicates with the service provider directly and not on behalf of a resource owner. |
Passwords expire.Usage See Prerequisites for Resource Owner Password Credentials .Chapter 2 Authentication Support 2-2Grant Type About the Grant Type Use Cases and Risks In this OAuth flow: The user clicks a link in the client application requesting access to protected resources.The client application requests the resource owners user name and password.The user logs in with their user name and password.The client application exchanges those credentials for an access token, and often a refresh token, from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server returns the access token to the client application.The client application uses the access token in an API call to invoke the integration.Chapter 2 Authentication Support 2-3Grant Type About the Grant Type Use Cases and Risks Client credentials The client credentials grant is used when the OAuth client itself owns the data and doesn't need delegated access from a resource owner.The client credentials grant provides a specific grant flow in which the resource owner (that is, the user) is not involved.When using this grant, the client application requests an access token only with its own credentials (the identifier and secret) or an assertion from the token endpoint and uses the access token on behalf of the client application itself.The token endpoint does not issue a refresh token.This is because refresh tokens are not supported by the client credentials grant.When the access token expires, the client application must request a new access token.Client credentials have the following characteristics: Are used by confidential OAuth clients.The OAuth client application communicates with the service provider directly and not on behalf of a resource owner.The flow is not redirection-based. |
Usage See Prerequisites for Resource Owner Password Credentials .Chapter 2 Authentication Support 2-2Grant Type About the Grant Type Use Cases and Risks In this OAuth flow: The user clicks a link in the client application requesting access to protected resources.The client application requests the resource owners user name and password.The user logs in with their user name and password.The client application exchanges those credentials for an access token, and often a refresh token, from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server returns the access token to the client application.The client application uses the access token in an API call to invoke the integration.Chapter 2 Authentication Support 2-3Grant Type About the Grant Type Use Cases and Risks Client credentials The client credentials grant is used when the OAuth client itself owns the data and doesn't need delegated access from a resource owner.The client credentials grant provides a specific grant flow in which the resource owner (that is, the user) is not involved.When using this grant, the client application requests an access token only with its own credentials (the identifier and secret) or an assertion from the token endpoint and uses the access token on behalf of the client application itself.The token endpoint does not issue a refresh token.This is because refresh tokens are not supported by the client credentials grant.When the access token expires, the client application must request a new access token.Client credentials have the following characteristics: Are used by confidential OAuth clients.The OAuth client application communicates with the service provider directly and not on behalf of a resource owner.The flow is not redirection-based.An access token is outside of the context of the end user. |
The client application requests the resource owners user name and password.The user logs in with their user name and password.The client application exchanges those credentials for an access token, and often a refresh token, from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server returns the access token to the client application.The client application uses the access token in an API call to invoke the integration.Chapter 2 Authentication Support 2-3Grant Type About the Grant Type Use Cases and Risks Client credentials The client credentials grant is used when the OAuth client itself owns the data and doesn't need delegated access from a resource owner.The client credentials grant provides a specific grant flow in which the resource owner (that is, the user) is not involved.When using this grant, the client application requests an access token only with its own credentials (the identifier and secret) or an assertion from the token endpoint and uses the access token on behalf of the client application itself.The token endpoint does not issue a refresh token.This is because refresh tokens are not supported by the client credentials grant.When the access token expires, the client application must request a new access token.Client credentials have the following characteristics: Are used by confidential OAuth clients.The OAuth client application communicates with the service provider directly and not on behalf of a resource owner.The flow is not redirection-based.An access token is outside of the context of the end user.In this OAuth flow: A user clicks a link in a web server client application to request access to protected resources. |
The user logs in with their user name and password.The client application exchanges those credentials for an access token, and often a refresh token, from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server returns the access token to the client application.The client application uses the access token in an API call to invoke the integration.Chapter 2 Authentication Support 2-3Grant Type About the Grant Type Use Cases and Risks Client credentials The client credentials grant is used when the OAuth client itself owns the data and doesn't need delegated access from a resource owner.The client credentials grant provides a specific grant flow in which the resource owner (that is, the user) is not involved.When using this grant, the client application requests an access token only with its own credentials (the identifier and secret) or an assertion from the token endpoint and uses the access token on behalf of the client application itself.The token endpoint does not issue a refresh token.This is because refresh tokens are not supported by the client credentials grant.When the access token expires, the client application must request a new access token.Client credentials have the following characteristics: Are used by confidential OAuth clients.The OAuth client application communicates with the service provider directly and not on behalf of a resource owner.The flow is not redirection-based.An access token is outside of the context of the end user.In this OAuth flow: A user clicks a link in a web server client application to request access to protected resources.The client application exchanges its credentials for an access token from the Oracle Identity Cloud Service authorization server. |
The client application exchanges those credentials for an access token, and often a refresh token, from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server returns the access token to the client application.The client application uses the access token in an API call to invoke the integration.Chapter 2 Authentication Support 2-3Grant Type About the Grant Type Use Cases and Risks Client credentials The client credentials grant is used when the OAuth client itself owns the data and doesn't need delegated access from a resource owner.The client credentials grant provides a specific grant flow in which the resource owner (that is, the user) is not involved.When using this grant, the client application requests an access token only with its own credentials (the identifier and secret) or an assertion from the token endpoint and uses the access token on behalf of the client application itself.The token endpoint does not issue a refresh token.This is because refresh tokens are not supported by the client credentials grant.When the access token expires, the client application must request a new access token.Client credentials have the following characteristics: Are used by confidential OAuth clients.The OAuth client application communicates with the service provider directly and not on behalf of a resource owner.The flow is not redirection-based.An access token is outside of the context of the end user.In this OAuth flow: A user clicks a link in a web server client application to request access to protected resources.The client application exchanges its credentials for an access token from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server validates the client credentials and returnsA OAuth client that uses the client credentials grant must have credentials on the authorization server, which means the client must be a confidential client. |
The Oracle Identity Cloud Service authorization server returns the access token to the client application.The client application uses the access token in an API call to invoke the integration.Chapter 2 Authentication Support 2-3Grant Type About the Grant Type Use Cases and Risks Client credentials The client credentials grant is used when the OAuth client itself owns the data and doesn't need delegated access from a resource owner.The client credentials grant provides a specific grant flow in which the resource owner (that is, the user) is not involved.When using this grant, the client application requests an access token only with its own credentials (the identifier and secret) or an assertion from the token endpoint and uses the access token on behalf of the client application itself.The token endpoint does not issue a refresh token.This is because refresh tokens are not supported by the client credentials grant.When the access token expires, the client application must request a new access token.Client credentials have the following characteristics: Are used by confidential OAuth clients.The OAuth client application communicates with the service provider directly and not on behalf of a resource owner.The flow is not redirection-based.An access token is outside of the context of the end user.In this OAuth flow: A user clicks a link in a web server client application to request access to protected resources.The client application exchanges its credentials for an access token from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server validates the client credentials and returnsA OAuth client that uses the client credentials grant must have credentials on the authorization server, which means the client must be a confidential client.With the client credentials grant, the integration server does not know the owner because the client does not need resource owner approval. |
The client application uses the access token in an API call to invoke the integration.Chapter 2 Authentication Support 2-3Grant Type About the Grant Type Use Cases and Risks Client credentials The client credentials grant is used when the OAuth client itself owns the data and doesn't need delegated access from a resource owner.The client credentials grant provides a specific grant flow in which the resource owner (that is, the user) is not involved.When using this grant, the client application requests an access token only with its own credentials (the identifier and secret) or an assertion from the token endpoint and uses the access token on behalf of the client application itself.The token endpoint does not issue a refresh token.This is because refresh tokens are not supported by the client credentials grant.When the access token expires, the client application must request a new access token.Client credentials have the following characteristics: Are used by confidential OAuth clients.The OAuth client application communicates with the service provider directly and not on behalf of a resource owner.The flow is not redirection-based.An access token is outside of the context of the end user.In this OAuth flow: A user clicks a link in a web server client application to request access to protected resources.The client application exchanges its credentials for an access token from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server validates the client credentials and returnsA OAuth client that uses the client credentials grant must have credentials on the authorization server, which means the client must be a confidential client.With the client credentials grant, the integration server does not know the owner because the client does not need resource owner approval.This grant flow is best-suited for when a service provider wants to provide some API methods for use by the client application in general, instead of methods that apply to a certain resource owner. |
The client credentials grant provides a specific grant flow in which the resource owner (that is, the user) is not involved.When using this grant, the client application requests an access token only with its own credentials (the identifier and secret) or an assertion from the token endpoint and uses the access token on behalf of the client application itself.The token endpoint does not issue a refresh token.This is because refresh tokens are not supported by the client credentials grant.When the access token expires, the client application must request a new access token.Client credentials have the following characteristics: Are used by confidential OAuth clients.The OAuth client application communicates with the service provider directly and not on behalf of a resource owner.The flow is not redirection-based.An access token is outside of the context of the end user.In this OAuth flow: A user clicks a link in a web server client application to request access to protected resources.The client application exchanges its credentials for an access token from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server validates the client credentials and returnsA OAuth client that uses the client credentials grant must have credentials on the authorization server, which means the client must be a confidential client.With the client credentials grant, the integration server does not know the owner because the client does not need resource owner approval.This grant flow is best-suited for when a service provider wants to provide some API methods for use by the client application in general, instead of methods that apply to a certain resource owner.Usage See Prerequisites for OAuth Client CredentialsChapter 2 Authentication Support 2-4Grant Type About the Grant Type Use Cases and Risks the access token to the client application. |
When using this grant, the client application requests an access token only with its own credentials (the identifier and secret) or an assertion from the token endpoint and uses the access token on behalf of the client application itself.The token endpoint does not issue a refresh token.This is because refresh tokens are not supported by the client credentials grant.When the access token expires, the client application must request a new access token.Client credentials have the following characteristics: Are used by confidential OAuth clients.The OAuth client application communicates with the service provider directly and not on behalf of a resource owner.The flow is not redirection-based.An access token is outside of the context of the end user.In this OAuth flow: A user clicks a link in a web server client application to request access to protected resources.The client application exchanges its credentials for an access token from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server validates the client credentials and returnsA OAuth client that uses the client credentials grant must have credentials on the authorization server, which means the client must be a confidential client.With the client credentials grant, the integration server does not know the owner because the client does not need resource owner approval.This grant flow is best-suited for when a service provider wants to provide some API methods for use by the client application in general, instead of methods that apply to a certain resource owner.Usage See Prerequisites for OAuth Client CredentialsChapter 2 Authentication Support 2-4Grant Type About the Grant Type Use Cases and Risks the access token to the client application.The client application uses the access token in an API call to invoke the integration. |
The token endpoint does not issue a refresh token.This is because refresh tokens are not supported by the client credentials grant.When the access token expires, the client application must request a new access token.Client credentials have the following characteristics: Are used by confidential OAuth clients.The OAuth client application communicates with the service provider directly and not on behalf of a resource owner.The flow is not redirection-based.An access token is outside of the context of the end user.In this OAuth flow: A user clicks a link in a web server client application to request access to protected resources.The client application exchanges its credentials for an access token from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server validates the client credentials and returnsA OAuth client that uses the client credentials grant must have credentials on the authorization server, which means the client must be a confidential client.With the client credentials grant, the integration server does not know the owner because the client does not need resource owner approval.This grant flow is best-suited for when a service provider wants to provide some API methods for use by the client application in general, instead of methods that apply to a certain resource owner.Usage See Prerequisites for OAuth Client CredentialsChapter 2 Authentication Support 2-4Grant Type About the Grant Type Use Cases and Risks the access token to the client application.The client application uses the access token in an API call to invoke the integration.Use OAuth 2.0 Grants To use an OAuth 2.0 grant type with the Oracle Utilities Adapter in Oracle Integration, you must perform the following prerequisites. |
This is because refresh tokens are not supported by the client credentials grant.When the access token expires, the client application must request a new access token.Client credentials have the following characteristics: Are used by confidential OAuth clients.The OAuth client application communicates with the service provider directly and not on behalf of a resource owner.The flow is not redirection-based.An access token is outside of the context of the end user.In this OAuth flow: A user clicks a link in a web server client application to request access to protected resources.The client application exchanges its credentials for an access token from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server validates the client credentials and returnsA OAuth client that uses the client credentials grant must have credentials on the authorization server, which means the client must be a confidential client.With the client credentials grant, the integration server does not know the owner because the client does not need resource owner approval.This grant flow is best-suited for when a service provider wants to provide some API methods for use by the client application in general, instead of methods that apply to a certain resource owner.Usage See Prerequisites for OAuth Client CredentialsChapter 2 Authentication Support 2-4Grant Type About the Grant Type Use Cases and Risks the access token to the client application.The client application uses the access token in an API call to invoke the integration.Use OAuth 2.0 Grants To use an OAuth 2.0 grant type with the Oracle Utilities Adapter in Oracle Integration, you must perform the following prerequisites.Prerequisites for All Grants Prerequisites for Resource Owner Password Credentials Prerequisites for OAuth Client Credentials Prerequisites for All Grants Perform the following tasks for each grant type you use. |
When the access token expires, the client application must request a new access token.Client credentials have the following characteristics: Are used by confidential OAuth clients.The OAuth client application communicates with the service provider directly and not on behalf of a resource owner.The flow is not redirection-based.An access token is outside of the context of the end user.In this OAuth flow: A user clicks a link in a web server client application to request access to protected resources.The client application exchanges its credentials for an access token from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server validates the client credentials and returnsA OAuth client that uses the client credentials grant must have credentials on the authorization server, which means the client must be a confidential client.With the client credentials grant, the integration server does not know the owner because the client does not need resource owner approval.This grant flow is best-suited for when a service provider wants to provide some API methods for use by the client application in general, instead of methods that apply to a certain resource owner.Usage See Prerequisites for OAuth Client CredentialsChapter 2 Authentication Support 2-4Grant Type About the Grant Type Use Cases and Risks the access token to the client application.The client application uses the access token in an API call to invoke the integration.Use OAuth 2.0 Grants To use an OAuth 2.0 grant type with the Oracle Utilities Adapter in Oracle Integration, you must perform the following prerequisites.Prerequisites for All Grants Prerequisites for Resource Owner Password Credentials Prerequisites for OAuth Client Credentials Prerequisites for All Grants Perform the following tasks for each grant type you use.Obtain the Oracle Identity Cloud Service URL. |
Client credentials have the following characteristics: Are used by confidential OAuth clients.The OAuth client application communicates with the service provider directly and not on behalf of a resource owner.The flow is not redirection-based.An access token is outside of the context of the end user.In this OAuth flow: A user clicks a link in a web server client application to request access to protected resources.The client application exchanges its credentials for an access token from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server validates the client credentials and returnsA OAuth client that uses the client credentials grant must have credentials on the authorization server, which means the client must be a confidential client.With the client credentials grant, the integration server does not know the owner because the client does not need resource owner approval.This grant flow is best-suited for when a service provider wants to provide some API methods for use by the client application in general, instead of methods that apply to a certain resource owner.Usage See Prerequisites for OAuth Client CredentialsChapter 2 Authentication Support 2-4Grant Type About the Grant Type Use Cases and Risks the access token to the client application.The client application uses the access token in an API call to invoke the integration.Use OAuth 2.0 Grants To use an OAuth 2.0 grant type with the Oracle Utilities Adapter in Oracle Integration, you must perform the following prerequisites.Prerequisites for All Grants Prerequisites for Resource Owner Password Credentials Prerequisites for OAuth Client Credentials Prerequisites for All Grants Perform the following tasks for each grant type you use.Obtain the Oracle Identity Cloud Service URL.1.Go to the URL for your Oracle Utilities application. |
The OAuth client application communicates with the service provider directly and not on behalf of a resource owner.The flow is not redirection-based.An access token is outside of the context of the end user.In this OAuth flow: A user clicks a link in a web server client application to request access to protected resources.The client application exchanges its credentials for an access token from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server validates the client credentials and returnsA OAuth client that uses the client credentials grant must have credentials on the authorization server, which means the client must be a confidential client.With the client credentials grant, the integration server does not know the owner because the client does not need resource owner approval.This grant flow is best-suited for when a service provider wants to provide some API methods for use by the client application in general, instead of methods that apply to a certain resource owner.Usage See Prerequisites for OAuth Client CredentialsChapter 2 Authentication Support 2-4Grant Type About the Grant Type Use Cases and Risks the access token to the client application.The client application uses the access token in an API call to invoke the integration.Use OAuth 2.0 Grants To use an OAuth 2.0 grant type with the Oracle Utilities Adapter in Oracle Integration, you must perform the following prerequisites.Prerequisites for All Grants Prerequisites for Resource Owner Password Credentials Prerequisites for OAuth Client Credentials Prerequisites for All Grants Perform the following tasks for each grant type you use.Obtain the Oracle Identity Cloud Service URL.1.Go to the URL for your Oracle Utilities application.You are redirected to a URL such as: https://idcs-c2881.identity.myhost.example.com/ui/v1/signin 2.Replace /signin with /adminconsole to access Oracle Identity Cloud Service. |
The flow is not redirection-based.An access token is outside of the context of the end user.In this OAuth flow: A user clicks a link in a web server client application to request access to protected resources.The client application exchanges its credentials for an access token from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server validates the client credentials and returnsA OAuth client that uses the client credentials grant must have credentials on the authorization server, which means the client must be a confidential client.With the client credentials grant, the integration server does not know the owner because the client does not need resource owner approval.This grant flow is best-suited for when a service provider wants to provide some API methods for use by the client application in general, instead of methods that apply to a certain resource owner.Usage See Prerequisites for OAuth Client CredentialsChapter 2 Authentication Support 2-4Grant Type About the Grant Type Use Cases and Risks the access token to the client application.The client application uses the access token in an API call to invoke the integration.Use OAuth 2.0 Grants To use an OAuth 2.0 grant type with the Oracle Utilities Adapter in Oracle Integration, you must perform the following prerequisites.Prerequisites for All Grants Prerequisites for Resource Owner Password Credentials Prerequisites for OAuth Client Credentials Prerequisites for All Grants Perform the following tasks for each grant type you use.Obtain the Oracle Identity Cloud Service URL.1.Go to the URL for your Oracle Utilities application.You are redirected to a URL such as: https://idcs-c2881.identity.myhost.example.com/ui/v1/signin 2.Replace /signin with /adminconsole to access Oracle Identity Cloud Service.For example: https://idcs-c2881.identity.myhost.example.com/ui/v1/adminconsole You'll be prompted to sign in again to the Oracle Identity Cloud Service Console. |
An access token is outside of the context of the end user.In this OAuth flow: A user clicks a link in a web server client application to request access to protected resources.The client application exchanges its credentials for an access token from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server validates the client credentials and returnsA OAuth client that uses the client credentials grant must have credentials on the authorization server, which means the client must be a confidential client.With the client credentials grant, the integration server does not know the owner because the client does not need resource owner approval.This grant flow is best-suited for when a service provider wants to provide some API methods for use by the client application in general, instead of methods that apply to a certain resource owner.Usage See Prerequisites for OAuth Client CredentialsChapter 2 Authentication Support 2-4Grant Type About the Grant Type Use Cases and Risks the access token to the client application.The client application uses the access token in an API call to invoke the integration.Use OAuth 2.0 Grants To use an OAuth 2.0 grant type with the Oracle Utilities Adapter in Oracle Integration, you must perform the following prerequisites.Prerequisites for All Grants Prerequisites for Resource Owner Password Credentials Prerequisites for OAuth Client Credentials Prerequisites for All Grants Perform the following tasks for each grant type you use.Obtain the Oracle Identity Cloud Service URL.1.Go to the URL for your Oracle Utilities application.You are redirected to a URL such as: https://idcs-c2881.identity.myhost.example.com/ui/v1/signin 2.Replace /signin with /adminconsole to access Oracle Identity Cloud Service.For example: https://idcs-c2881.identity.myhost.example.com/ui/v1/adminconsole You'll be prompted to sign in again to the Oracle Identity Cloud Service Console.3.Log in to the Oracle Identity Cloud Service Console with your identity domain administrator credentials. |
In this OAuth flow: A user clicks a link in a web server client application to request access to protected resources.The client application exchanges its credentials for an access token from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server validates the client credentials and returnsA OAuth client that uses the client credentials grant must have credentials on the authorization server, which means the client must be a confidential client.With the client credentials grant, the integration server does not know the owner because the client does not need resource owner approval.This grant flow is best-suited for when a service provider wants to provide some API methods for use by the client application in general, instead of methods that apply to a certain resource owner.Usage See Prerequisites for OAuth Client CredentialsChapter 2 Authentication Support 2-4Grant Type About the Grant Type Use Cases and Risks the access token to the client application.The client application uses the access token in an API call to invoke the integration.Use OAuth 2.0 Grants To use an OAuth 2.0 grant type with the Oracle Utilities Adapter in Oracle Integration, you must perform the following prerequisites.Prerequisites for All Grants Prerequisites for Resource Owner Password Credentials Prerequisites for OAuth Client Credentials Prerequisites for All Grants Perform the following tasks for each grant type you use.Obtain the Oracle Identity Cloud Service URL.1.Go to the URL for your Oracle Utilities application.You are redirected to a URL such as: https://idcs-c2881.identity.myhost.example.com/ui/v1/signin 2.Replace /signin with /adminconsole to access Oracle Identity Cloud Service.For example: https://idcs-c2881.identity.myhost.example.com/ui/v1/adminconsole You'll be prompted to sign in again to the Oracle Identity Cloud Service Console.3.Log in to the Oracle Identity Cloud Service Console with your identity domain administrator credentials.Check the Oracle Utilities application in Oracle Identity Cloud Service. |
The client application exchanges its credentials for an access token from the Oracle Identity Cloud Service authorization server.The Oracle Identity Cloud Service authorization server validates the client credentials and returnsA OAuth client that uses the client credentials grant must have credentials on the authorization server, which means the client must be a confidential client.With the client credentials grant, the integration server does not know the owner because the client does not need resource owner approval.This grant flow is best-suited for when a service provider wants to provide some API methods for use by the client application in general, instead of methods that apply to a certain resource owner.Usage See Prerequisites for OAuth Client CredentialsChapter 2 Authentication Support 2-4Grant Type About the Grant Type Use Cases and Risks the access token to the client application.The client application uses the access token in an API call to invoke the integration.Use OAuth 2.0 Grants To use an OAuth 2.0 grant type with the Oracle Utilities Adapter in Oracle Integration, you must perform the following prerequisites.Prerequisites for All Grants Prerequisites for Resource Owner Password Credentials Prerequisites for OAuth Client Credentials Prerequisites for All Grants Perform the following tasks for each grant type you use.Obtain the Oracle Identity Cloud Service URL.1.Go to the URL for your Oracle Utilities application.You are redirected to a URL such as: https://idcs-c2881.identity.myhost.example.com/ui/v1/signin 2.Replace /signin with /adminconsole to access Oracle Identity Cloud Service.For example: https://idcs-c2881.identity.myhost.example.com/ui/v1/adminconsole You'll be prompted to sign in again to the Oracle Identity Cloud Service Console.3.Log in to the Oracle Identity Cloud Service Console with your identity domain administrator credentials.Check the Oracle Utilities application in Oracle Identity Cloud Service.When an Oracle Utilities application instance is provisioned, an Oracle Identity Cloud Service application is created for that application instance. |
The Oracle Identity Cloud Service authorization server validates the client credentials and returnsA OAuth client that uses the client credentials grant must have credentials on the authorization server, which means the client must be a confidential client.With the client credentials grant, the integration server does not know the owner because the client does not need resource owner approval.This grant flow is best-suited for when a service provider wants to provide some API methods for use by the client application in general, instead of methods that apply to a certain resource owner.Usage See Prerequisites for OAuth Client CredentialsChapter 2 Authentication Support 2-4Grant Type About the Grant Type Use Cases and Risks the access token to the client application.The client application uses the access token in an API call to invoke the integration.Use OAuth 2.0 Grants To use an OAuth 2.0 grant type with the Oracle Utilities Adapter in Oracle Integration, you must perform the following prerequisites.Prerequisites for All Grants Prerequisites for Resource Owner Password Credentials Prerequisites for OAuth Client Credentials Prerequisites for All Grants Perform the following tasks for each grant type you use.Obtain the Oracle Identity Cloud Service URL.1.Go to the URL for your Oracle Utilities application.You are redirected to a URL such as: https://idcs-c2881.identity.myhost.example.com/ui/v1/signin 2.Replace /signin with /adminconsole to access Oracle Identity Cloud Service.For example: https://idcs-c2881.identity.myhost.example.com/ui/v1/adminconsole You'll be prompted to sign in again to the Oracle Identity Cloud Service Console.3.Log in to the Oracle Identity Cloud Service Console with your identity domain administrator credentials.Check the Oracle Utilities application in Oracle Identity Cloud Service.When an Oracle Utilities application instance is provisioned, an Oracle Identity Cloud Service application is created for that application instance.The application name is composed as follows: product -domain tenant suffix sequential_number For example: CCS-PRODC12345CMETERDATA0 CCS-PRODC12345FIELDSERVICE1Chapter 2 Authentication Support 2-51.To request creation of a new OAuth client application, create a cloud operations service request and provide the following information: Environment(s) where the OAuth client application is needed (for example, PROD, TEST01, or DEV). |
With the client credentials grant, the integration server does not know the owner because the client does not need resource owner approval.This grant flow is best-suited for when a service provider wants to provide some API methods for use by the client application in general, instead of methods that apply to a certain resource owner.Usage See Prerequisites for OAuth Client CredentialsChapter 2 Authentication Support 2-4Grant Type About the Grant Type Use Cases and Risks the access token to the client application.The client application uses the access token in an API call to invoke the integration.Use OAuth 2.0 Grants To use an OAuth 2.0 grant type with the Oracle Utilities Adapter in Oracle Integration, you must perform the following prerequisites.Prerequisites for All Grants Prerequisites for Resource Owner Password Credentials Prerequisites for OAuth Client Credentials Prerequisites for All Grants Perform the following tasks for each grant type you use.Obtain the Oracle Identity Cloud Service URL.1.Go to the URL for your Oracle Utilities application.You are redirected to a URL such as: https://idcs-c2881.identity.myhost.example.com/ui/v1/signin 2.Replace /signin with /adminconsole to access Oracle Identity Cloud Service.For example: https://idcs-c2881.identity.myhost.example.com/ui/v1/adminconsole You'll be prompted to sign in again to the Oracle Identity Cloud Service Console.3.Log in to the Oracle Identity Cloud Service Console with your identity domain administrator credentials.Check the Oracle Utilities application in Oracle Identity Cloud Service.When an Oracle Utilities application instance is provisioned, an Oracle Identity Cloud Service application is created for that application instance.The application name is composed as follows: product -domain tenant suffix sequential_number For example: CCS-PRODC12345CMETERDATA0 CCS-PRODC12345FIELDSERVICE1Chapter 2 Authentication Support 2-51.To request creation of a new OAuth client application, create a cloud operations service request and provide the following information: Environment(s) where the OAuth client application is needed (for example, PROD, TEST01, or DEV).Client name suffix: Use a distinct name that may suggest the functional purpose of the integration. |
This grant flow is best-suited for when a service provider wants to provide some API methods for use by the client application in general, instead of methods that apply to a certain resource owner.Usage See Prerequisites for OAuth Client CredentialsChapter 2 Authentication Support 2-4Grant Type About the Grant Type Use Cases and Risks the access token to the client application.The client application uses the access token in an API call to invoke the integration.Use OAuth 2.0 Grants To use an OAuth 2.0 grant type with the Oracle Utilities Adapter in Oracle Integration, you must perform the following prerequisites.Prerequisites for All Grants Prerequisites for Resource Owner Password Credentials Prerequisites for OAuth Client Credentials Prerequisites for All Grants Perform the following tasks for each grant type you use.Obtain the Oracle Identity Cloud Service URL.1.Go to the URL for your Oracle Utilities application.You are redirected to a URL such as: https://idcs-c2881.identity.myhost.example.com/ui/v1/signin 2.Replace /signin with /adminconsole to access Oracle Identity Cloud Service.For example: https://idcs-c2881.identity.myhost.example.com/ui/v1/adminconsole You'll be prompted to sign in again to the Oracle Identity Cloud Service Console.3.Log in to the Oracle Identity Cloud Service Console with your identity domain administrator credentials.Check the Oracle Utilities application in Oracle Identity Cloud Service.When an Oracle Utilities application instance is provisioned, an Oracle Identity Cloud Service application is created for that application instance.The application name is composed as follows: product -domain tenant suffix sequential_number For example: CCS-PRODC12345CMETERDATA0 CCS-PRODC12345FIELDSERVICE1Chapter 2 Authentication Support 2-51.To request creation of a new OAuth client application, create a cloud operations service request and provide the following information: Environment(s) where the OAuth client application is needed (for example, PROD, TEST01, or DEV).Client name suffix: Use a distinct name that may suggest the functional purpose of the integration.Provide a meaningful description of the integration point. |
Usage See Prerequisites for OAuth Client CredentialsChapter 2 Authentication Support 2-4Grant Type About the Grant Type Use Cases and Risks the access token to the client application.The client application uses the access token in an API call to invoke the integration.Use OAuth 2.0 Grants To use an OAuth 2.0 grant type with the Oracle Utilities Adapter in Oracle Integration, you must perform the following prerequisites.Prerequisites for All Grants Prerequisites for Resource Owner Password Credentials Prerequisites for OAuth Client Credentials Prerequisites for All Grants Perform the following tasks for each grant type you use.Obtain the Oracle Identity Cloud Service URL.1.Go to the URL for your Oracle Utilities application.You are redirected to a URL such as: https://idcs-c2881.identity.myhost.example.com/ui/v1/signin 2.Replace /signin with /adminconsole to access Oracle Identity Cloud Service.For example: https://idcs-c2881.identity.myhost.example.com/ui/v1/adminconsole You'll be prompted to sign in again to the Oracle Identity Cloud Service Console.3.Log in to the Oracle Identity Cloud Service Console with your identity domain administrator credentials.Check the Oracle Utilities application in Oracle Identity Cloud Service.When an Oracle Utilities application instance is provisioned, an Oracle Identity Cloud Service application is created for that application instance.The application name is composed as follows: product -domain tenant suffix sequential_number For example: CCS-PRODC12345CMETERDATA0 CCS-PRODC12345FIELDSERVICE1Chapter 2 Authentication Support 2-51.To request creation of a new OAuth client application, create a cloud operations service request and provide the following information: Environment(s) where the OAuth client application is needed (for example, PROD, TEST01, or DEV).Client name suffix: Use a distinct name that may suggest the functional purpose of the integration.Provide a meaningful description of the integration point.Client type (trusted or confidential) and client certificate: The integration requirements may call for a trusted client and the external application may also supply its own certificate. |
The client application uses the access token in an API call to invoke the integration.Use OAuth 2.0 Grants To use an OAuth 2.0 grant type with the Oracle Utilities Adapter in Oracle Integration, you must perform the following prerequisites.Prerequisites for All Grants Prerequisites for Resource Owner Password Credentials Prerequisites for OAuth Client Credentials Prerequisites for All Grants Perform the following tasks for each grant type you use.Obtain the Oracle Identity Cloud Service URL.1.Go to the URL for your Oracle Utilities application.You are redirected to a URL such as: https://idcs-c2881.identity.myhost.example.com/ui/v1/signin 2.Replace /signin with /adminconsole to access Oracle Identity Cloud Service.For example: https://idcs-c2881.identity.myhost.example.com/ui/v1/adminconsole You'll be prompted to sign in again to the Oracle Identity Cloud Service Console.3.Log in to the Oracle Identity Cloud Service Console with your identity domain administrator credentials.Check the Oracle Utilities application in Oracle Identity Cloud Service.When an Oracle Utilities application instance is provisioned, an Oracle Identity Cloud Service application is created for that application instance.The application name is composed as follows: product -domain tenant suffix sequential_number For example: CCS-PRODC12345CMETERDATA0 CCS-PRODC12345FIELDSERVICE1Chapter 2 Authentication Support 2-51.To request creation of a new OAuth client application, create a cloud operations service request and provide the following information: Environment(s) where the OAuth client application is needed (for example, PROD, TEST01, or DEV).Client name suffix: Use a distinct name that may suggest the functional purpose of the integration.Provide a meaningful description of the integration point.Client type (trusted or confidential) and client certificate: The integration requirements may call for a trusted client and the external application may also supply its own certificate.Otherwise, Oracle Identity Cloud Service creates a trusted client with its internal native certificate. |
Use OAuth 2.0 Grants To use an OAuth 2.0 grant type with the Oracle Utilities Adapter in Oracle Integration, you must perform the following prerequisites.Prerequisites for All Grants Prerequisites for Resource Owner Password Credentials Prerequisites for OAuth Client Credentials Prerequisites for All Grants Perform the following tasks for each grant type you use.Obtain the Oracle Identity Cloud Service URL.1.Go to the URL for your Oracle Utilities application.You are redirected to a URL such as: https://idcs-c2881.identity.myhost.example.com/ui/v1/signin 2.Replace /signin with /adminconsole to access Oracle Identity Cloud Service.For example: https://idcs-c2881.identity.myhost.example.com/ui/v1/adminconsole You'll be prompted to sign in again to the Oracle Identity Cloud Service Console.3.Log in to the Oracle Identity Cloud Service Console with your identity domain administrator credentials.Check the Oracle Utilities application in Oracle Identity Cloud Service.When an Oracle Utilities application instance is provisioned, an Oracle Identity Cloud Service application is created for that application instance.The application name is composed as follows: product -domain tenant suffix sequential_number For example: CCS-PRODC12345CMETERDATA0 CCS-PRODC12345FIELDSERVICE1Chapter 2 Authentication Support 2-51.To request creation of a new OAuth client application, create a cloud operations service request and provide the following information: Environment(s) where the OAuth client application is needed (for example, PROD, TEST01, or DEV).Client name suffix: Use a distinct name that may suggest the functional purpose of the integration.Provide a meaningful description of the integration point.Client type (trusted or confidential) and client certificate: The integration requirements may call for a trusted client and the external application may also supply its own certificate.Otherwise, Oracle Identity Cloud Service creates a trusted client with its internal native certificate.OAuth flow for your intended integration: Client credentials, JWT assertion, and authorization code flows are currently supported. |
Prerequisites for All Grants Prerequisites for Resource Owner Password Credentials Prerequisites for OAuth Client Credentials Prerequisites for All Grants Perform the following tasks for each grant type you use.Obtain the Oracle Identity Cloud Service URL.1.Go to the URL for your Oracle Utilities application.You are redirected to a URL such as: https://idcs-c2881.identity.myhost.example.com/ui/v1/signin 2.Replace /signin with /adminconsole to access Oracle Identity Cloud Service.For example: https://idcs-c2881.identity.myhost.example.com/ui/v1/adminconsole You'll be prompted to sign in again to the Oracle Identity Cloud Service Console.3.Log in to the Oracle Identity Cloud Service Console with your identity domain administrator credentials.Check the Oracle Utilities application in Oracle Identity Cloud Service.When an Oracle Utilities application instance is provisioned, an Oracle Identity Cloud Service application is created for that application instance.The application name is composed as follows: product -domain tenant suffix sequential_number For example: CCS-PRODC12345CMETERDATA0 CCS-PRODC12345FIELDSERVICE1Chapter 2 Authentication Support 2-51.To request creation of a new OAuth client application, create a cloud operations service request and provide the following information: Environment(s) where the OAuth client application is needed (for example, PROD, TEST01, or DEV).Client name suffix: Use a distinct name that may suggest the functional purpose of the integration.Provide a meaningful description of the integration point.Client type (trusted or confidential) and client certificate: The integration requirements may call for a trusted client and the external application may also supply its own certificate.Otherwise, Oracle Identity Cloud Service creates a trusted client with its internal native certificate.OAuth flow for your intended integration: Client credentials, JWT assertion, and authorization code flows are currently supported.For the authorization code flow, you can also supply your own redirect URL. |
Obtain the Oracle Identity Cloud Service URL.1.Go to the URL for your Oracle Utilities application.You are redirected to a URL such as: https://idcs-c2881.identity.myhost.example.com/ui/v1/signin 2.Replace /signin with /adminconsole to access Oracle Identity Cloud Service.For example: https://idcs-c2881.identity.myhost.example.com/ui/v1/adminconsole You'll be prompted to sign in again to the Oracle Identity Cloud Service Console.3.Log in to the Oracle Identity Cloud Service Console with your identity domain administrator credentials.Check the Oracle Utilities application in Oracle Identity Cloud Service.When an Oracle Utilities application instance is provisioned, an Oracle Identity Cloud Service application is created for that application instance.The application name is composed as follows: product -domain tenant suffix sequential_number For example: CCS-PRODC12345CMETERDATA0 CCS-PRODC12345FIELDSERVICE1Chapter 2 Authentication Support 2-51.To request creation of a new OAuth client application, create a cloud operations service request and provide the following information: Environment(s) where the OAuth client application is needed (for example, PROD, TEST01, or DEV).Client name suffix: Use a distinct name that may suggest the functional purpose of the integration.Provide a meaningful description of the integration point.Client type (trusted or confidential) and client certificate: The integration requirements may call for a trusted client and the external application may also supply its own certificate.Otherwise, Oracle Identity Cloud Service creates a trusted client with its internal native certificate.OAuth flow for your intended integration: Client credentials, JWT assertion, and authorization code flows are currently supported.For the authorization code flow, you can also supply your own redirect URL.Scope: You can define the OAuth client application with access to either REST or SOAP APIs or both REST and SOAP APIs. |
1.Go to the URL for your Oracle Utilities application.You are redirected to a URL such as: https://idcs-c2881.identity.myhost.example.com/ui/v1/signin 2.Replace /signin with /adminconsole to access Oracle Identity Cloud Service.For example: https://idcs-c2881.identity.myhost.example.com/ui/v1/adminconsole You'll be prompted to sign in again to the Oracle Identity Cloud Service Console.3.Log in to the Oracle Identity Cloud Service Console with your identity domain administrator credentials.Check the Oracle Utilities application in Oracle Identity Cloud Service.When an Oracle Utilities application instance is provisioned, an Oracle Identity Cloud Service application is created for that application instance.The application name is composed as follows: product -domain tenant suffix sequential_number For example: CCS-PRODC12345CMETERDATA0 CCS-PRODC12345FIELDSERVICE1Chapter 2 Authentication Support 2-51.To request creation of a new OAuth client application, create a cloud operations service request and provide the following information: Environment(s) where the OAuth client application is needed (for example, PROD, TEST01, or DEV).Client name suffix: Use a distinct name that may suggest the functional purpose of the integration.Provide a meaningful description of the integration point.Client type (trusted or confidential) and client certificate: The integration requirements may call for a trusted client and the external application may also supply its own certificate.Otherwise, Oracle Identity Cloud Service creates a trusted client with its internal native certificate.OAuth flow for your intended integration: Client credentials, JWT assertion, and authorization code flows are currently supported.For the authorization code flow, you can also supply your own redirect URL.Scope: You can define the OAuth client application with access to either REST or SOAP APIs or both REST and SOAP APIs.The Oracle Utilities Cloud Operations team creates the OAuth client using the input provided in the service request. |
You are redirected to a URL such as: https://idcs-c2881.identity.myhost.example.com/ui/v1/signin 2.Replace /signin with /adminconsole to access Oracle Identity Cloud Service.For example: https://idcs-c2881.identity.myhost.example.com/ui/v1/adminconsole You'll be prompted to sign in again to the Oracle Identity Cloud Service Console.3.Log in to the Oracle Identity Cloud Service Console with your identity domain administrator credentials.Check the Oracle Utilities application in Oracle Identity Cloud Service.When an Oracle Utilities application instance is provisioned, an Oracle Identity Cloud Service application is created for that application instance.The application name is composed as follows: product -domain tenant suffix sequential_number For example: CCS-PRODC12345CMETERDATA0 CCS-PRODC12345FIELDSERVICE1Chapter 2 Authentication Support 2-51.To request creation of a new OAuth client application, create a cloud operations service request and provide the following information: Environment(s) where the OAuth client application is needed (for example, PROD, TEST01, or DEV).Client name suffix: Use a distinct name that may suggest the functional purpose of the integration.Provide a meaningful description of the integration point.Client type (trusted or confidential) and client certificate: The integration requirements may call for a trusted client and the external application may also supply its own certificate.Otherwise, Oracle Identity Cloud Service creates a trusted client with its internal native certificate.OAuth flow for your intended integration: Client credentials, JWT assertion, and authorization code flows are currently supported.For the authorization code flow, you can also supply your own redirect URL.Scope: You can define the OAuth client application with access to either REST or SOAP APIs or both REST and SOAP APIs.The Oracle Utilities Cloud Operations team creates the OAuth client using the input provided in the service request.1.Log in to Oracle Identity Cloud Service to get your application. |
For example: https://idcs-c2881.identity.myhost.example.com/ui/v1/adminconsole You'll be prompted to sign in again to the Oracle Identity Cloud Service Console.3.Log in to the Oracle Identity Cloud Service Console with your identity domain administrator credentials.Check the Oracle Utilities application in Oracle Identity Cloud Service.When an Oracle Utilities application instance is provisioned, an Oracle Identity Cloud Service application is created for that application instance.The application name is composed as follows: product -domain tenant suffix sequential_number For example: CCS-PRODC12345CMETERDATA0 CCS-PRODC12345FIELDSERVICE1Chapter 2 Authentication Support 2-51.To request creation of a new OAuth client application, create a cloud operations service request and provide the following information: Environment(s) where the OAuth client application is needed (for example, PROD, TEST01, or DEV).Client name suffix: Use a distinct name that may suggest the functional purpose of the integration.Provide a meaningful description of the integration point.Client type (trusted or confidential) and client certificate: The integration requirements may call for a trusted client and the external application may also supply its own certificate.Otherwise, Oracle Identity Cloud Service creates a trusted client with its internal native certificate.OAuth flow for your intended integration: Client credentials, JWT assertion, and authorization code flows are currently supported.For the authorization code flow, you can also supply your own redirect URL.Scope: You can define the OAuth client application with access to either REST or SOAP APIs or both REST and SOAP APIs.The Oracle Utilities Cloud Operations team creates the OAuth client using the input provided in the service request.1.Log in to Oracle Identity Cloud Service to get your application.2.Go to Oracle Cloud Services and find the application with the above name to access the application. |
3.Log in to the Oracle Identity Cloud Service Console with your identity domain administrator credentials.Check the Oracle Utilities application in Oracle Identity Cloud Service.When an Oracle Utilities application instance is provisioned, an Oracle Identity Cloud Service application is created for that application instance.The application name is composed as follows: product -domain tenant suffix sequential_number For example: CCS-PRODC12345CMETERDATA0 CCS-PRODC12345FIELDSERVICE1Chapter 2 Authentication Support 2-51.To request creation of a new OAuth client application, create a cloud operations service request and provide the following information: Environment(s) where the OAuth client application is needed (for example, PROD, TEST01, or DEV).Client name suffix: Use a distinct name that may suggest the functional purpose of the integration.Provide a meaningful description of the integration point.Client type (trusted or confidential) and client certificate: The integration requirements may call for a trusted client and the external application may also supply its own certificate.Otherwise, Oracle Identity Cloud Service creates a trusted client with its internal native certificate.OAuth flow for your intended integration: Client credentials, JWT assertion, and authorization code flows are currently supported.For the authorization code flow, you can also supply your own redirect URL.Scope: You can define the OAuth client application with access to either REST or SOAP APIs or both REST and SOAP APIs.The Oracle Utilities Cloud Operations team creates the OAuth client using the input provided in the service request.1.Log in to Oracle Identity Cloud Service to get your application.2.Go to Oracle Cloud Services and find the application with the above name to access the application.Prerequisites for Resource Owner Password Credentials Perform the following tasks. |
Check the Oracle Utilities application in Oracle Identity Cloud Service.When an Oracle Utilities application instance is provisioned, an Oracle Identity Cloud Service application is created for that application instance.The application name is composed as follows: product -domain tenant suffix sequential_number For example: CCS-PRODC12345CMETERDATA0 CCS-PRODC12345FIELDSERVICE1Chapter 2 Authentication Support 2-51.To request creation of a new OAuth client application, create a cloud operations service request and provide the following information: Environment(s) where the OAuth client application is needed (for example, PROD, TEST01, or DEV).Client name suffix: Use a distinct name that may suggest the functional purpose of the integration.Provide a meaningful description of the integration point.Client type (trusted or confidential) and client certificate: The integration requirements may call for a trusted client and the external application may also supply its own certificate.Otherwise, Oracle Identity Cloud Service creates a trusted client with its internal native certificate.OAuth flow for your intended integration: Client credentials, JWT assertion, and authorization code flows are currently supported.For the authorization code flow, you can also supply your own redirect URL.Scope: You can define the OAuth client application with access to either REST or SOAP APIs or both REST and SOAP APIs.The Oracle Utilities Cloud Operations team creates the OAuth client using the input provided in the service request.1.Log in to Oracle Identity Cloud Service to get your application.2.Go to Oracle Cloud Services and find the application with the above name to access the application.Prerequisites for Resource Owner Password Credentials Perform the following tasks.Validate the Oracle Integration application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application. |
When an Oracle Utilities application instance is provisioned, an Oracle Identity Cloud Service application is created for that application instance.The application name is composed as follows: product -domain tenant suffix sequential_number For example: CCS-PRODC12345CMETERDATA0 CCS-PRODC12345FIELDSERVICE1Chapter 2 Authentication Support 2-51.To request creation of a new OAuth client application, create a cloud operations service request and provide the following information: Environment(s) where the OAuth client application is needed (for example, PROD, TEST01, or DEV).Client name suffix: Use a distinct name that may suggest the functional purpose of the integration.Provide a meaningful description of the integration point.Client type (trusted or confidential) and client certificate: The integration requirements may call for a trusted client and the external application may also supply its own certificate.Otherwise, Oracle Identity Cloud Service creates a trusted client with its internal native certificate.OAuth flow for your intended integration: Client credentials, JWT assertion, and authorization code flows are currently supported.For the authorization code flow, you can also supply your own redirect URL.Scope: You can define the OAuth client application with access to either REST or SOAP APIs or both REST and SOAP APIs.The Oracle Utilities Cloud Operations team creates the OAuth client using the input provided in the service request.1.Log in to Oracle Identity Cloud Service to get your application.2.Go to Oracle Cloud Services and find the application with the above name to access the application.Prerequisites for Resource Owner Password Credentials Perform the following tasks.Validate the Oracle Integration application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Resource Owner and Refresh Token for Allowed Grant Types are enabled. |
The application name is composed as follows: product -domain tenant suffix sequential_number For example: CCS-PRODC12345CMETERDATA0 CCS-PRODC12345FIELDSERVICE1Chapter 2 Authentication Support 2-51.To request creation of a new OAuth client application, create a cloud operations service request and provide the following information: Environment(s) where the OAuth client application is needed (for example, PROD, TEST01, or DEV).Client name suffix: Use a distinct name that may suggest the functional purpose of the integration.Provide a meaningful description of the integration point.Client type (trusted or confidential) and client certificate: The integration requirements may call for a trusted client and the external application may also supply its own certificate.Otherwise, Oracle Identity Cloud Service creates a trusted client with its internal native certificate.OAuth flow for your intended integration: Client credentials, JWT assertion, and authorization code flows are currently supported.For the authorization code flow, you can also supply your own redirect URL.Scope: You can define the OAuth client application with access to either REST or SOAP APIs or both REST and SOAP APIs.The Oracle Utilities Cloud Operations team creates the OAuth client using the input provided in the service request.1.Log in to Oracle Identity Cloud Service to get your application.2.Go to Oracle Cloud Services and find the application with the above name to access the application.Prerequisites for Resource Owner Password Credentials Perform the following tasks.Validate the Oracle Integration application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Resource Owner and Refresh Token for Allowed Grant Types are enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application. |
Client name suffix: Use a distinct name that may suggest the functional purpose of the integration.Provide a meaningful description of the integration point.Client type (trusted or confidential) and client certificate: The integration requirements may call for a trusted client and the external application may also supply its own certificate.Otherwise, Oracle Identity Cloud Service creates a trusted client with its internal native certificate.OAuth flow for your intended integration: Client credentials, JWT assertion, and authorization code flows are currently supported.For the authorization code flow, you can also supply your own redirect URL.Scope: You can define the OAuth client application with access to either REST or SOAP APIs or both REST and SOAP APIs.The Oracle Utilities Cloud Operations team creates the OAuth client using the input provided in the service request.1.Log in to Oracle Identity Cloud Service to get your application.2.Go to Oracle Cloud Services and find the application with the above name to access the application.Prerequisites for Resource Owner Password Credentials Perform the following tasks.Validate the Oracle Integration application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Resource Owner and Refresh Token for Allowed Grant Types are enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.4.Verify that the Is Refresh Token Allowed option is enabled. |
Provide a meaningful description of the integration point.Client type (trusted or confidential) and client certificate: The integration requirements may call for a trusted client and the external application may also supply its own certificate.Otherwise, Oracle Identity Cloud Service creates a trusted client with its internal native certificate.OAuth flow for your intended integration: Client credentials, JWT assertion, and authorization code flows are currently supported.For the authorization code flow, you can also supply your own redirect URL.Scope: You can define the OAuth client application with access to either REST or SOAP APIs or both REST and SOAP APIs.The Oracle Utilities Cloud Operations team creates the OAuth client using the input provided in the service request.1.Log in to Oracle Identity Cloud Service to get your application.2.Go to Oracle Cloud Services and find the application with the above name to access the application.Prerequisites for Resource Owner Password Credentials Perform the following tasks.Validate the Oracle Integration application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Resource Owner and Refresh Token for Allowed Grant Types are enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.4.Verify that the Is Refresh Token Allowed option is enabled.Chapter 2 Authentication Support 2-6 The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided. |
Client type (trusted or confidential) and client certificate: The integration requirements may call for a trusted client and the external application may also supply its own certificate.Otherwise, Oracle Identity Cloud Service creates a trusted client with its internal native certificate.OAuth flow for your intended integration: Client credentials, JWT assertion, and authorization code flows are currently supported.For the authorization code flow, you can also supply your own redirect URL.Scope: You can define the OAuth client application with access to either REST or SOAP APIs or both REST and SOAP APIs.The Oracle Utilities Cloud Operations team creates the OAuth client using the input provided in the service request.1.Log in to Oracle Identity Cloud Service to get your application.2.Go to Oracle Cloud Services and find the application with the above name to access the application.Prerequisites for Resource Owner Password Credentials Perform the following tasks.Validate the Oracle Integration application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Resource Owner and Refresh Token for Allowed Grant Types are enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.4.Verify that the Is Refresh Token Allowed option is enabled.Chapter 2 Authentication Support 2-6 The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.5.Add the appropriate user(s) to the various Oracle Application roles. |
Otherwise, Oracle Identity Cloud Service creates a trusted client with its internal native certificate.OAuth flow for your intended integration: Client credentials, JWT assertion, and authorization code flows are currently supported.For the authorization code flow, you can also supply your own redirect URL.Scope: You can define the OAuth client application with access to either REST or SOAP APIs or both REST and SOAP APIs.The Oracle Utilities Cloud Operations team creates the OAuth client using the input provided in the service request.1.Log in to Oracle Identity Cloud Service to get your application.2.Go to Oracle Cloud Services and find the application with the above name to access the application.Prerequisites for Resource Owner Password Credentials Perform the following tasks.Validate the Oracle Integration application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Resource Owner and Refresh Token for Allowed Grant Types are enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.4.Verify that the Is Refresh Token Allowed option is enabled.Chapter 2 Authentication Support 2-6 The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.5.Add the appropriate user(s) to the various Oracle Application roles.For standard/ production configurations, use the ServiceUser role. |
OAuth flow for your intended integration: Client credentials, JWT assertion, and authorization code flows are currently supported.For the authorization code flow, you can also supply your own redirect URL.Scope: You can define the OAuth client application with access to either REST or SOAP APIs or both REST and SOAP APIs.The Oracle Utilities Cloud Operations team creates the OAuth client using the input provided in the service request.1.Log in to Oracle Identity Cloud Service to get your application.2.Go to Oracle Cloud Services and find the application with the above name to access the application.Prerequisites for Resource Owner Password Credentials Perform the following tasks.Validate the Oracle Integration application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Resource Owner and Refresh Token for Allowed Grant Types are enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.4.Verify that the Is Refresh Token Allowed option is enabled.Chapter 2 Authentication Support 2-6 The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.5.Add the appropriate user(s) to the various Oracle Application roles.For standard/ production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .) |
For the authorization code flow, you can also supply your own redirect URL.Scope: You can define the OAuth client application with access to either REST or SOAP APIs or both REST and SOAP APIs.The Oracle Utilities Cloud Operations team creates the OAuth client using the input provided in the service request.1.Log in to Oracle Identity Cloud Service to get your application.2.Go to Oracle Cloud Services and find the application with the above name to access the application.Prerequisites for Resource Owner Password Credentials Perform the following tasks.Validate the Oracle Integration application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Resource Owner and Refresh Token for Allowed Grant Types are enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.4.Verify that the Is Refresh Token Allowed option is enabled.Chapter 2 Authentication Support 2-6 The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.5.Add the appropriate user(s) to the various Oracle Application roles.For standard/ production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)6.To assign the user, go to the Application Roles section of the application and assign the user for AppWebServices . |
Scope: You can define the OAuth client application with access to either REST or SOAP APIs or both REST and SOAP APIs.The Oracle Utilities Cloud Operations team creates the OAuth client using the input provided in the service request.1.Log in to Oracle Identity Cloud Service to get your application.2.Go to Oracle Cloud Services and find the application with the above name to access the application.Prerequisites for Resource Owner Password Credentials Perform the following tasks.Validate the Oracle Integration application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Resource Owner and Refresh Token for Allowed Grant Types are enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.4.Verify that the Is Refresh Token Allowed option is enabled.Chapter 2 Authentication Support 2-6 The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.5.Add the appropriate user(s) to the various Oracle Application roles.For standard/ production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)6.To assign the user, go to the Application Roles section of the application and assign the user for AppWebServices .Chapter 2 Authentication Support 2-7 Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application with an OAuth Utilities Connection. |
The Oracle Utilities Cloud Operations team creates the OAuth client using the input provided in the service request.1.Log in to Oracle Identity Cloud Service to get your application.2.Go to Oracle Cloud Services and find the application with the above name to access the application.Prerequisites for Resource Owner Password Credentials Perform the following tasks.Validate the Oracle Integration application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Resource Owner and Refresh Token for Allowed Grant Types are enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.4.Verify that the Is Refresh Token Allowed option is enabled.Chapter 2 Authentication Support 2-6 The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.5.Add the appropriate user(s) to the various Oracle Application roles.For standard/ production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)6.To assign the user, go to the Application Roles section of the application and assign the user for AppWebServices .Chapter 2 Authentication Support 2-7 Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application with an OAuth Utilities Connection.Add this application as a confidential application. |
1.Log in to Oracle Identity Cloud Service to get your application.2.Go to Oracle Cloud Services and find the application with the above name to access the application.Prerequisites for Resource Owner Password Credentials Perform the following tasks.Validate the Oracle Integration application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Resource Owner and Refresh Token for Allowed Grant Types are enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.4.Verify that the Is Refresh Token Allowed option is enabled.Chapter 2 Authentication Support 2-6 The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.5.Add the appropriate user(s) to the various Oracle Application roles.For standard/ production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)6.To assign the user, go to the Application Roles section of the application and assign the user for AppWebServices .Chapter 2 Authentication Support 2-7 Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application with an OAuth Utilities Connection.Add this application as a confidential application.2.Click Add. |
2.Go to Oracle Cloud Services and find the application with the above name to access the application.Prerequisites for Resource Owner Password Credentials Perform the following tasks.Validate the Oracle Integration application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Resource Owner and Refresh Token for Allowed Grant Types are enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.4.Verify that the Is Refresh Token Allowed option is enabled.Chapter 2 Authentication Support 2-6 The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.5.Add the appropriate user(s) to the various Oracle Application roles.For standard/ production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)6.To assign the user, go to the Application Roles section of the application and assign the user for AppWebServices .Chapter 2 Authentication Support 2-7 Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application with an OAuth Utilities Connection.Add this application as a confidential application.2.Click Add.3.Select Confidential Application . |
Prerequisites for Resource Owner Password Credentials Perform the following tasks.Validate the Oracle Integration application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Resource Owner and Refresh Token for Allowed Grant Types are enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.4.Verify that the Is Refresh Token Allowed option is enabled.Chapter 2 Authentication Support 2-6 The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.5.Add the appropriate user(s) to the various Oracle Application roles.For standard/ production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)6.To assign the user, go to the Application Roles section of the application and assign the user for AppWebServices .Chapter 2 Authentication Support 2-7 Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application with an OAuth Utilities Connection.Add this application as a confidential application.2.Click Add.3.Select Confidential Application .4.Complete the Details page, and go to the Client page. |
Validate the Oracle Integration application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Resource Owner and Refresh Token for Allowed Grant Types are enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.4.Verify that the Is Refresh Token Allowed option is enabled.Chapter 2 Authentication Support 2-6 The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.5.Add the appropriate user(s) to the various Oracle Application roles.For standard/ production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)6.To assign the user, go to the Application Roles section of the application and assign the user for AppWebServices .Chapter 2 Authentication Support 2-7 Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application with an OAuth Utilities Connection.Add this application as a confidential application.2.Click Add.3.Select Confidential Application .4.Complete the Details page, and go to the Client page.5.On the Client page, select Configure this application as a client now and add the following. |
2.Verify that Resource Owner and Refresh Token for Allowed Grant Types are enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.4.Verify that the Is Refresh Token Allowed option is enabled.Chapter 2 Authentication Support 2-6 The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.5.Add the appropriate user(s) to the various Oracle Application roles.For standard/ production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)6.To assign the user, go to the Application Roles section of the application and assign the user for AppWebServices .Chapter 2 Authentication Support 2-7 Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application with an OAuth Utilities Connection.Add this application as a confidential application.2.Click Add.3.Select Confidential Application .4.Complete the Details page, and go to the Client page.5.On the Client page, select Configure this application as a client now and add the following.a.Select Resource Owner and Refresh Token for Allowed Grant Types . |
3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.4.Verify that the Is Refresh Token Allowed option is enabled.Chapter 2 Authentication Support 2-6 The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.5.Add the appropriate user(s) to the various Oracle Application roles.For standard/ production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)6.To assign the user, go to the Application Roles section of the application and assign the user for AppWebServices .Chapter 2 Authentication Support 2-7 Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application with an OAuth Utilities Connection.Add this application as a confidential application.2.Click Add.3.Select Confidential Application .4.Complete the Details page, and go to the Client page.5.On the Client page, select Configure this application as a client now and add the following.a.Select Resource Owner and Refresh Token for Allowed Grant Types .b.Select Specific in the Authorized Resources section.Chapter 2 Authentication Support 2-8 c.Click Add Scope under the Resources section. |
4.Verify that the Is Refresh Token Allowed option is enabled.Chapter 2 Authentication Support 2-6 The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.5.Add the appropriate user(s) to the various Oracle Application roles.For standard/ production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)6.To assign the user, go to the Application Roles section of the application and assign the user for AppWebServices .Chapter 2 Authentication Support 2-7 Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application with an OAuth Utilities Connection.Add this application as a confidential application.2.Click Add.3.Select Confidential Application .4.Complete the Details page, and go to the Client page.5.On the Client page, select Configure this application as a client now and add the following.a.Select Resource Owner and Refresh Token for Allowed Grant Types .b.Select Specific in the Authorized Resources section.Chapter 2 Authentication Support 2-8 c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application. |
Chapter 2 Authentication Support 2-6 The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.5.Add the appropriate user(s) to the various Oracle Application roles.For standard/ production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)6.To assign the user, go to the Application Roles section of the application and assign the user for AppWebServices .Chapter 2 Authentication Support 2-7 Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application with an OAuth Utilities Connection.Add this application as a confidential application.2.Click Add.3.Select Confidential Application .4.Complete the Details page, and go to the Client page.5.On the Client page, select Configure this application as a client now and add the following.a.Select Resource Owner and Refresh Token for Allowed Grant Types .b.Select Specific in the Authorized Resources section.Chapter 2 Authentication Support 2-8 c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST ( /rest/* ) or SOAP( /soap/* ) APIs or both REST and SOAP APIs ( /*), and click >. |
5.Add the appropriate user(s) to the various Oracle Application roles.For standard/ production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)6.To assign the user, go to the Application Roles section of the application and assign the user for AppWebServices .Chapter 2 Authentication Support 2-7 Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application with an OAuth Utilities Connection.Add this application as a confidential application.2.Click Add.3.Select Confidential Application .4.Complete the Details page, and go to the Client page.5.On the Client page, select Configure this application as a client now and add the following.a.Select Resource Owner and Refresh Token for Allowed Grant Types .b.Select Specific in the Authorized Resources section.Chapter 2 Authentication Support 2-8 c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST ( /rest/* ) or SOAP( /soap/* ) APIs or both REST and SOAP APIs ( /*), and click >.Chapter 2 Authentication Support 2-9 f.Save your changes. |
For standard/ production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)6.To assign the user, go to the Application Roles section of the application and assign the user for AppWebServices .Chapter 2 Authentication Support 2-7 Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application with an OAuth Utilities Connection.Add this application as a confidential application.2.Click Add.3.Select Confidential Application .4.Complete the Details page, and go to the Client page.5.On the Client page, select Configure this application as a client now and add the following.a.Select Resource Owner and Refresh Token for Allowed Grant Types .b.Select Specific in the Authorized Resources section.Chapter 2 Authentication Support 2-8 c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST ( /rest/* ) or SOAP( /soap/* ) APIs or both REST and SOAP APIs ( /*), and click >.Chapter 2 Authentication Support 2-9 f.Save your changes.6.Click through the remaining wizard pages without making changes and save the application. |
(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)6.To assign the user, go to the Application Roles section of the application and assign the user for AppWebServices .Chapter 2 Authentication Support 2-7 Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application with an OAuth Utilities Connection.Add this application as a confidential application.2.Click Add.3.Select Confidential Application .4.Complete the Details page, and go to the Client page.5.On the Client page, select Configure this application as a client now and add the following.a.Select Resource Owner and Refresh Token for Allowed Grant Types .b.Select Specific in the Authorized Resources section.Chapter 2 Authentication Support 2-8 c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST ( /rest/* ) or SOAP( /soap/* ) APIs or both REST and SOAP APIs ( /*), and click >.Chapter 2 Authentication Support 2-9 f.Save your changes.6.Click through the remaining wizard pages without making changes and save the application.7.Activate the application for use. |
6.To assign the user, go to the Application Roles section of the application and assign the user for AppWebServices .Chapter 2 Authentication Support 2-7 Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application with an OAuth Utilities Connection.Add this application as a confidential application.2.Click Add.3.Select Confidential Application .4.Complete the Details page, and go to the Client page.5.On the Client page, select Configure this application as a client now and add the following.a.Select Resource Owner and Refresh Token for Allowed Grant Types .b.Select Specific in the Authorized Resources section.Chapter 2 Authentication Support 2-8 c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST ( /rest/* ) or SOAP( /soap/* ) APIs or both REST and SOAP APIs ( /*), and click >.Chapter 2 Authentication Support 2-9 f.Save your changes.6.Click through the remaining wizard pages without making changes and save the application.7.Activate the application for use.Validate the client application: 1.To fetch the access client, make a request to Oracle Identity Cloud Service with the user name and password in the payload. |
Chapter 2 Authentication Support 2-7 Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application with an OAuth Utilities Connection.Add this application as a confidential application.2.Click Add.3.Select Confidential Application .4.Complete the Details page, and go to the Client page.5.On the Client page, select Configure this application as a client now and add the following.a.Select Resource Owner and Refresh Token for Allowed Grant Types .b.Select Specific in the Authorized Resources section.Chapter 2 Authentication Support 2-8 c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST ( /rest/* ) or SOAP( /soap/* ) APIs or both REST and SOAP APIs ( /*), and click >.Chapter 2 Authentication Support 2-9 f.Save your changes.6.Click through the remaining wizard pages without making changes and save the application.7.Activate the application for use.Validate the client application: 1.To fetch the access client, make a request to Oracle Identity Cloud Service with the user name and password in the payload.Note: Add offline_access in the scope to fetch the request refresh token as part of the response. |
Add this application as a confidential application.2.Click Add.3.Select Confidential Application .4.Complete the Details page, and go to the Client page.5.On the Client page, select Configure this application as a client now and add the following.a.Select Resource Owner and Refresh Token for Allowed Grant Types .b.Select Specific in the Authorized Resources section.Chapter 2 Authentication Support 2-8 c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST ( /rest/* ) or SOAP( /soap/* ) APIs or both REST and SOAP APIs ( /*), and click >.Chapter 2 Authentication Support 2-9 f.Save your changes.6.Click through the remaining wizard pages without making changes and save the application.7.Activate the application for use.Validate the client application: 1.To fetch the access client, make a request to Oracle Identity Cloud Service with the user name and password in the payload.Note: Add offline_access in the scope to fetch the request refresh token as part of the response.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x- www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS- Service-Instance>.identity.oraclecloud.com/oauth2/v1/token -d 'grant_type=password&username=<user- name>&password=<password>&scope=<App_Scope>%20offline_access' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <username> - user for token needs to be issued (must be in serviceuser role). |
2.Click Add.3.Select Confidential Application .4.Complete the Details page, and go to the Client page.5.On the Client page, select Configure this application as a client now and add the following.a.Select Resource Owner and Refresh Token for Allowed Grant Types .b.Select Specific in the Authorized Resources section.Chapter 2 Authentication Support 2-8 c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST ( /rest/* ) or SOAP( /soap/* ) APIs or both REST and SOAP APIs ( /*), and click >.Chapter 2 Authentication Support 2-9 f.Save your changes.6.Click through the remaining wizard pages without making changes and save the application.7.Activate the application for use.Validate the client application: 1.To fetch the access client, make a request to Oracle Identity Cloud Service with the user name and password in the payload.Note: Add offline_access in the scope to fetch the request refresh token as part of the response.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x- www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS- Service-Instance>.identity.oraclecloud.com/oauth2/v1/token -d 'grant_type=password&username=<user- name>&password=<password>&scope=<App_Scope>%20offline_access' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <username> - user for token needs to be issued (must be in serviceuser role).#### <password> - password for above user #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content- Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=password&username=sampleUser&password=SamplePassword& scope=https://<Resource_APP_Audience>/rest/*%20offline_access' 2.Capture the access_token and refresh_token from the response. |
3.Select Confidential Application .4.Complete the Details page, and go to the Client page.5.On the Client page, select Configure this application as a client now and add the following.a.Select Resource Owner and Refresh Token for Allowed Grant Types .b.Select Specific in the Authorized Resources section.Chapter 2 Authentication Support 2-8 c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST ( /rest/* ) or SOAP( /soap/* ) APIs or both REST and SOAP APIs ( /*), and click >.Chapter 2 Authentication Support 2-9 f.Save your changes.6.Click through the remaining wizard pages without making changes and save the application.7.Activate the application for use.Validate the client application: 1.To fetch the access client, make a request to Oracle Identity Cloud Service with the user name and password in the payload.Note: Add offline_access in the scope to fetch the request refresh token as part of the response.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x- www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS- Service-Instance>.identity.oraclecloud.com/oauth2/v1/token -d 'grant_type=password&username=<user- name>&password=<password>&scope=<App_Scope>%20offline_access' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <username> - user for token needs to be issued (must be in serviceuser role).#### <password> - password for above user #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content- Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=password&username=sampleUser&password=SamplePassword& scope=https://<Resource_APP_Audience>/rest/*%20offline_access' 2.Capture the access_token and refresh_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer", "expires_in": 3600,Chapter 2 Authentication Support 2-10 "refresh_token": "AQAgY2MzNjVlOTVhOTRh...vM5S0MkrFSpzc=" } 3.Use the access_token in the authorization header to invoke the Oracle Utilities application endpoint. |
4.Complete the Details page, and go to the Client page.5.On the Client page, select Configure this application as a client now and add the following.a.Select Resource Owner and Refresh Token for Allowed Grant Types .b.Select Specific in the Authorized Resources section.Chapter 2 Authentication Support 2-8 c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST ( /rest/* ) or SOAP( /soap/* ) APIs or both REST and SOAP APIs ( /*), and click >.Chapter 2 Authentication Support 2-9 f.Save your changes.6.Click through the remaining wizard pages without making changes and save the application.7.Activate the application for use.Validate the client application: 1.To fetch the access client, make a request to Oracle Identity Cloud Service with the user name and password in the payload.Note: Add offline_access in the scope to fetch the request refresh token as part of the response.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x- www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS- Service-Instance>.identity.oraclecloud.com/oauth2/v1/token -d 'grant_type=password&username=<user- name>&password=<password>&scope=<App_Scope>%20offline_access' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <username> - user for token needs to be issued (must be in serviceuser role).#### <password> - password for above user #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content- Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=password&username=sampleUser&password=SamplePassword& scope=https://<Resource_APP_Audience>/rest/*%20offline_access' 2.Capture the access_token and refresh_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer", "expires_in": 3600,Chapter 2 Authentication Support 2-10 "refresh_token": "AQAgY2MzNjVlOTVhOTRh...vM5S0MkrFSpzc=" } 3.Use the access_token in the authorization header to invoke the Oracle Utilities application endpoint.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token, use the refresh token and make a request to Oracle Identity Cloud Service. |
5.On the Client page, select Configure this application as a client now and add the following.a.Select Resource Owner and Refresh Token for Allowed Grant Types .b.Select Specific in the Authorized Resources section.Chapter 2 Authentication Support 2-8 c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST ( /rest/* ) or SOAP( /soap/* ) APIs or both REST and SOAP APIs ( /*), and click >.Chapter 2 Authentication Support 2-9 f.Save your changes.6.Click through the remaining wizard pages without making changes and save the application.7.Activate the application for use.Validate the client application: 1.To fetch the access client, make a request to Oracle Identity Cloud Service with the user name and password in the payload.Note: Add offline_access in the scope to fetch the request refresh token as part of the response.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x- www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS- Service-Instance>.identity.oraclecloud.com/oauth2/v1/token -d 'grant_type=password&username=<user- name>&password=<password>&scope=<App_Scope>%20offline_access' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <username> - user for token needs to be issued (must be in serviceuser role).#### <password> - password for above user #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content- Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=password&username=sampleUser&password=SamplePassword& scope=https://<Resource_APP_Audience>/rest/*%20offline_access' 2.Capture the access_token and refresh_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer", "expires_in": 3600,Chapter 2 Authentication Support 2-10 "refresh_token": "AQAgY2MzNjVlOTVhOTRh...vM5S0MkrFSpzc=" } 3.Use the access_token in the authorization header to invoke the Oracle Utilities application endpoint.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token, use the refresh token and make a request to Oracle Identity Cloud Service.5.Capture the access_token and refresh_token from the response for further use. |
a.Select Resource Owner and Refresh Token for Allowed Grant Types .b.Select Specific in the Authorized Resources section.Chapter 2 Authentication Support 2-8 c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST ( /rest/* ) or SOAP( /soap/* ) APIs or both REST and SOAP APIs ( /*), and click >.Chapter 2 Authentication Support 2-9 f.Save your changes.6.Click through the remaining wizard pages without making changes and save the application.7.Activate the application for use.Validate the client application: 1.To fetch the access client, make a request to Oracle Identity Cloud Service with the user name and password in the payload.Note: Add offline_access in the scope to fetch the request refresh token as part of the response.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x- www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS- Service-Instance>.identity.oraclecloud.com/oauth2/v1/token -d 'grant_type=password&username=<user- name>&password=<password>&scope=<App_Scope>%20offline_access' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <username> - user for token needs to be issued (must be in serviceuser role).#### <password> - password for above user #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content- Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=password&username=sampleUser&password=SamplePassword& scope=https://<Resource_APP_Audience>/rest/*%20offline_access' 2.Capture the access_token and refresh_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer", "expires_in": 3600,Chapter 2 Authentication Support 2-10 "refresh_token": "AQAgY2MzNjVlOTVhOTRh...vM5S0MkrFSpzc=" } 3.Use the access_token in the authorization header to invoke the Oracle Utilities application endpoint.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token, use the refresh token and make a request to Oracle Identity Cloud Service.5.Capture the access_token and refresh_token from the response for further use.curl -i -H 'Authorization: Basic <base64-clientid-secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=refresh_token&refresh_token=<refresh_token>' ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/oauth2/v1/ token -d 'grant_type=refresh_token&refresh_token=AQAgY2MzNjVlOTVhOTRh...vM5S0Mk rFSpzc=' Prerequisites for OAuth Client Credentials Perform the following tasks. |
b.Select Specific in the Authorized Resources section.Chapter 2 Authentication Support 2-8 c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST ( /rest/* ) or SOAP( /soap/* ) APIs or both REST and SOAP APIs ( /*), and click >.Chapter 2 Authentication Support 2-9 f.Save your changes.6.Click through the remaining wizard pages without making changes and save the application.7.Activate the application for use.Validate the client application: 1.To fetch the access client, make a request to Oracle Identity Cloud Service with the user name and password in the payload.Note: Add offline_access in the scope to fetch the request refresh token as part of the response.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x- www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS- Service-Instance>.identity.oraclecloud.com/oauth2/v1/token -d 'grant_type=password&username=<user- name>&password=<password>&scope=<App_Scope>%20offline_access' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <username> - user for token needs to be issued (must be in serviceuser role).#### <password> - password for above user #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content- Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=password&username=sampleUser&password=SamplePassword& scope=https://<Resource_APP_Audience>/rest/*%20offline_access' 2.Capture the access_token and refresh_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer", "expires_in": 3600,Chapter 2 Authentication Support 2-10 "refresh_token": "AQAgY2MzNjVlOTVhOTRh...vM5S0MkrFSpzc=" } 3.Use the access_token in the authorization header to invoke the Oracle Utilities application endpoint.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token, use the refresh token and make a request to Oracle Identity Cloud Service.5.Capture the access_token and refresh_token from the response for further use.curl -i -H 'Authorization: Basic <base64-clientid-secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=refresh_token&refresh_token=<refresh_token>' ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/oauth2/v1/ token -d 'grant_type=refresh_token&refresh_token=AQAgY2MzNjVlOTVhOTRh...vM5S0Mk rFSpzc=' Prerequisites for OAuth Client Credentials Perform the following tasks.Validate the Oracle Utilities application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application. |
d.Find the Oracle Utilities application.e.Add the scope containing access to either REST ( /rest/* ) or SOAP( /soap/* ) APIs or both REST and SOAP APIs ( /*), and click >.Chapter 2 Authentication Support 2-9 f.Save your changes.6.Click through the remaining wizard pages without making changes and save the application.7.Activate the application for use.Validate the client application: 1.To fetch the access client, make a request to Oracle Identity Cloud Service with the user name and password in the payload.Note: Add offline_access in the scope to fetch the request refresh token as part of the response.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x- www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS- Service-Instance>.identity.oraclecloud.com/oauth2/v1/token -d 'grant_type=password&username=<user- name>&password=<password>&scope=<App_Scope>%20offline_access' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <username> - user for token needs to be issued (must be in serviceuser role).#### <password> - password for above user #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content- Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=password&username=sampleUser&password=SamplePassword& scope=https://<Resource_APP_Audience>/rest/*%20offline_access' 2.Capture the access_token and refresh_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer", "expires_in": 3600,Chapter 2 Authentication Support 2-10 "refresh_token": "AQAgY2MzNjVlOTVhOTRh...vM5S0MkrFSpzc=" } 3.Use the access_token in the authorization header to invoke the Oracle Utilities application endpoint.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token, use the refresh token and make a request to Oracle Identity Cloud Service.5.Capture the access_token and refresh_token from the response for further use.curl -i -H 'Authorization: Basic <base64-clientid-secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=refresh_token&refresh_token=<refresh_token>' ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/oauth2/v1/ token -d 'grant_type=refresh_token&refresh_token=AQAgY2MzNjVlOTVhOTRh...vM5S0Mk rFSpzc=' Prerequisites for OAuth Client Credentials Perform the following tasks.Validate the Oracle Utilities application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Client Credentials for Allowed Grant Types is enabled. |
e.Add the scope containing access to either REST ( /rest/* ) or SOAP( /soap/* ) APIs or both REST and SOAP APIs ( /*), and click >.Chapter 2 Authentication Support 2-9 f.Save your changes.6.Click through the remaining wizard pages without making changes and save the application.7.Activate the application for use.Validate the client application: 1.To fetch the access client, make a request to Oracle Identity Cloud Service with the user name and password in the payload.Note: Add offline_access in the scope to fetch the request refresh token as part of the response.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x- www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS- Service-Instance>.identity.oraclecloud.com/oauth2/v1/token -d 'grant_type=password&username=<user- name>&password=<password>&scope=<App_Scope>%20offline_access' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <username> - user for token needs to be issued (must be in serviceuser role).#### <password> - password for above user #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content- Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=password&username=sampleUser&password=SamplePassword& scope=https://<Resource_APP_Audience>/rest/*%20offline_access' 2.Capture the access_token and refresh_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer", "expires_in": 3600,Chapter 2 Authentication Support 2-10 "refresh_token": "AQAgY2MzNjVlOTVhOTRh...vM5S0MkrFSpzc=" } 3.Use the access_token in the authorization header to invoke the Oracle Utilities application endpoint.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token, use the refresh token and make a request to Oracle Identity Cloud Service.5.Capture the access_token and refresh_token from the response for further use.curl -i -H 'Authorization: Basic <base64-clientid-secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=refresh_token&refresh_token=<refresh_token>' ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/oauth2/v1/ token -d 'grant_type=refresh_token&refresh_token=AQAgY2MzNjVlOTVhOTRh...vM5S0Mk rFSpzc=' Prerequisites for OAuth Client Credentials Perform the following tasks.Validate the Oracle Utilities application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Client Credentials for Allowed Grant Types is enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application. |
Chapter 2 Authentication Support 2-9 f.Save your changes.6.Click through the remaining wizard pages without making changes and save the application.7.Activate the application for use.Validate the client application: 1.To fetch the access client, make a request to Oracle Identity Cloud Service with the user name and password in the payload.Note: Add offline_access in the scope to fetch the request refresh token as part of the response.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x- www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS- Service-Instance>.identity.oraclecloud.com/oauth2/v1/token -d 'grant_type=password&username=<user- name>&password=<password>&scope=<App_Scope>%20offline_access' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <username> - user for token needs to be issued (must be in serviceuser role).#### <password> - password for above user #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content- Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=password&username=sampleUser&password=SamplePassword& scope=https://<Resource_APP_Audience>/rest/*%20offline_access' 2.Capture the access_token and refresh_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer", "expires_in": 3600,Chapter 2 Authentication Support 2-10 "refresh_token": "AQAgY2MzNjVlOTVhOTRh...vM5S0MkrFSpzc=" } 3.Use the access_token in the authorization header to invoke the Oracle Utilities application endpoint.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token, use the refresh token and make a request to Oracle Identity Cloud Service.5.Capture the access_token and refresh_token from the response for further use.curl -i -H 'Authorization: Basic <base64-clientid-secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=refresh_token&refresh_token=<refresh_token>' ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/oauth2/v1/ token -d 'grant_type=refresh_token&refresh_token=AQAgY2MzNjVlOTVhOTRh...vM5S0Mk rFSpzc=' Prerequisites for OAuth Client Credentials Perform the following tasks.Validate the Oracle Utilities application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Client Credentials for Allowed Grant Types is enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided. |
6.Click through the remaining wizard pages without making changes and save the application.7.Activate the application for use.Validate the client application: 1.To fetch the access client, make a request to Oracle Identity Cloud Service with the user name and password in the payload.Note: Add offline_access in the scope to fetch the request refresh token as part of the response.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x- www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS- Service-Instance>.identity.oraclecloud.com/oauth2/v1/token -d 'grant_type=password&username=<user- name>&password=<password>&scope=<App_Scope>%20offline_access' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <username> - user for token needs to be issued (must be in serviceuser role).#### <password> - password for above user #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content- Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=password&username=sampleUser&password=SamplePassword& scope=https://<Resource_APP_Audience>/rest/*%20offline_access' 2.Capture the access_token and refresh_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer", "expires_in": 3600,Chapter 2 Authentication Support 2-10 "refresh_token": "AQAgY2MzNjVlOTVhOTRh...vM5S0MkrFSpzc=" } 3.Use the access_token in the authorization header to invoke the Oracle Utilities application endpoint.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token, use the refresh token and make a request to Oracle Identity Cloud Service.5.Capture the access_token and refresh_token from the response for further use.curl -i -H 'Authorization: Basic <base64-clientid-secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=refresh_token&refresh_token=<refresh_token>' ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/oauth2/v1/ token -d 'grant_type=refresh_token&refresh_token=AQAgY2MzNjVlOTVhOTRh...vM5S0Mk rFSpzc=' Prerequisites for OAuth Client Credentials Perform the following tasks.Validate the Oracle Utilities application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Client Credentials for Allowed Grant Types is enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.4.Add the appropriate user(s) to the various Oracle Utilities application roles. |
7.Activate the application for use.Validate the client application: 1.To fetch the access client, make a request to Oracle Identity Cloud Service with the user name and password in the payload.Note: Add offline_access in the scope to fetch the request refresh token as part of the response.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x- www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS- Service-Instance>.identity.oraclecloud.com/oauth2/v1/token -d 'grant_type=password&username=<user- name>&password=<password>&scope=<App_Scope>%20offline_access' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <username> - user for token needs to be issued (must be in serviceuser role).#### <password> - password for above user #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content- Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=password&username=sampleUser&password=SamplePassword& scope=https://<Resource_APP_Audience>/rest/*%20offline_access' 2.Capture the access_token and refresh_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer", "expires_in": 3600,Chapter 2 Authentication Support 2-10 "refresh_token": "AQAgY2MzNjVlOTVhOTRh...vM5S0MkrFSpzc=" } 3.Use the access_token in the authorization header to invoke the Oracle Utilities application endpoint.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token, use the refresh token and make a request to Oracle Identity Cloud Service.5.Capture the access_token and refresh_token from the response for further use.curl -i -H 'Authorization: Basic <base64-clientid-secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=refresh_token&refresh_token=<refresh_token>' ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/oauth2/v1/ token -d 'grant_type=refresh_token&refresh_token=AQAgY2MzNjVlOTVhOTRh...vM5S0Mk rFSpzc=' Prerequisites for OAuth Client Credentials Perform the following tasks.Validate the Oracle Utilities application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Client Credentials for Allowed Grant Types is enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.4.Add the appropriate user(s) to the various Oracle Utilities application roles.For standard/production configurations, use the ServiceUser role. |
Validate the client application: 1.To fetch the access client, make a request to Oracle Identity Cloud Service with the user name and password in the payload.Note: Add offline_access in the scope to fetch the request refresh token as part of the response.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x- www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS- Service-Instance>.identity.oraclecloud.com/oauth2/v1/token -d 'grant_type=password&username=<user- name>&password=<password>&scope=<App_Scope>%20offline_access' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <username> - user for token needs to be issued (must be in serviceuser role).#### <password> - password for above user #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content- Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=password&username=sampleUser&password=SamplePassword& scope=https://<Resource_APP_Audience>/rest/*%20offline_access' 2.Capture the access_token and refresh_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer", "expires_in": 3600,Chapter 2 Authentication Support 2-10 "refresh_token": "AQAgY2MzNjVlOTVhOTRh...vM5S0MkrFSpzc=" } 3.Use the access_token in the authorization header to invoke the Oracle Utilities application endpoint.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token, use the refresh token and make a request to Oracle Identity Cloud Service.5.Capture the access_token and refresh_token from the response for further use.curl -i -H 'Authorization: Basic <base64-clientid-secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=refresh_token&refresh_token=<refresh_token>' ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/oauth2/v1/ token -d 'grant_type=refresh_token&refresh_token=AQAgY2MzNjVlOTVhOTRh...vM5S0Mk rFSpzc=' Prerequisites for OAuth Client Credentials Perform the following tasks.Validate the Oracle Utilities application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Client Credentials for Allowed Grant Types is enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.4.Add the appropriate user(s) to the various Oracle Utilities application roles.For standard/production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 . |
Note: Add offline_access in the scope to fetch the request refresh token as part of the response.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x- www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS- Service-Instance>.identity.oraclecloud.com/oauth2/v1/token -d 'grant_type=password&username=<user- name>&password=<password>&scope=<App_Scope>%20offline_access' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <username> - user for token needs to be issued (must be in serviceuser role).#### <password> - password for above user #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content- Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=password&username=sampleUser&password=SamplePassword& scope=https://<Resource_APP_Audience>/rest/*%20offline_access' 2.Capture the access_token and refresh_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer", "expires_in": 3600,Chapter 2 Authentication Support 2-10 "refresh_token": "AQAgY2MzNjVlOTVhOTRh...vM5S0MkrFSpzc=" } 3.Use the access_token in the authorization header to invoke the Oracle Utilities application endpoint.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token, use the refresh token and make a request to Oracle Identity Cloud Service.5.Capture the access_token and refresh_token from the response for further use.curl -i -H 'Authorization: Basic <base64-clientid-secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=refresh_token&refresh_token=<refresh_token>' ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/oauth2/v1/ token -d 'grant_type=refresh_token&refresh_token=AQAgY2MzNjVlOTVhOTRh...vM5S0Mk rFSpzc=' Prerequisites for OAuth Client Credentials Perform the following tasks.Validate the Oracle Utilities application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Client Credentials for Allowed Grant Types is enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.4.Add the appropriate user(s) to the various Oracle Utilities application roles.For standard/production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)Chapter 2 Authentication Support 2-115.To assign the user, go to the Application Roles section of the application under AppWebServices . |
##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x- www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS- Service-Instance>.identity.oraclecloud.com/oauth2/v1/token -d 'grant_type=password&username=<user- name>&password=<password>&scope=<App_Scope>%20offline_access' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <username> - user for token needs to be issued (must be in serviceuser role).#### <password> - password for above user #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content- Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=password&username=sampleUser&password=SamplePassword& scope=https://<Resource_APP_Audience>/rest/*%20offline_access' 2.Capture the access_token and refresh_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer", "expires_in": 3600,Chapter 2 Authentication Support 2-10 "refresh_token": "AQAgY2MzNjVlOTVhOTRh...vM5S0MkrFSpzc=" } 3.Use the access_token in the authorization header to invoke the Oracle Utilities application endpoint.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token, use the refresh token and make a request to Oracle Identity Cloud Service.5.Capture the access_token and refresh_token from the response for further use.curl -i -H 'Authorization: Basic <base64-clientid-secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=refresh_token&refresh_token=<refresh_token>' ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/oauth2/v1/ token -d 'grant_type=refresh_token&refresh_token=AQAgY2MzNjVlOTVhOTRh...vM5S0Mk rFSpzc=' Prerequisites for OAuth Client Credentials Perform the following tasks.Validate the Oracle Utilities application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Client Credentials for Allowed Grant Types is enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.4.Add the appropriate user(s) to the various Oracle Utilities application roles.For standard/production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)Chapter 2 Authentication Support 2-115.To assign the user, go to the Application Roles section of the application under AppWebServices .Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application API with an OAuth Utilities Connection. |
#### <password> - password for above user #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content- Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=password&username=sampleUser&password=SamplePassword& scope=https://<Resource_APP_Audience>/rest/*%20offline_access' 2.Capture the access_token and refresh_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer", "expires_in": 3600,Chapter 2 Authentication Support 2-10 "refresh_token": "AQAgY2MzNjVlOTVhOTRh...vM5S0MkrFSpzc=" } 3.Use the access_token in the authorization header to invoke the Oracle Utilities application endpoint.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token, use the refresh token and make a request to Oracle Identity Cloud Service.5.Capture the access_token and refresh_token from the response for further use.curl -i -H 'Authorization: Basic <base64-clientid-secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=refresh_token&refresh_token=<refresh_token>' ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/oauth2/v1/ token -d 'grant_type=refresh_token&refresh_token=AQAgY2MzNjVlOTVhOTRh...vM5S0Mk rFSpzc=' Prerequisites for OAuth Client Credentials Perform the following tasks.Validate the Oracle Utilities application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Client Credentials for Allowed Grant Types is enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.4.Add the appropriate user(s) to the various Oracle Utilities application roles.For standard/production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)Chapter 2 Authentication Support 2-115.To assign the user, go to the Application Roles section of the application under AppWebServices .Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application API with an OAuth Utilities Connection.The application is added as a confidential application. |
{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer", "expires_in": 3600,Chapter 2 Authentication Support 2-10 "refresh_token": "AQAgY2MzNjVlOTVhOTRh...vM5S0MkrFSpzc=" } 3.Use the access_token in the authorization header to invoke the Oracle Utilities application endpoint.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token, use the refresh token and make a request to Oracle Identity Cloud Service.5.Capture the access_token and refresh_token from the response for further use.curl -i -H 'Authorization: Basic <base64-clientid-secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=refresh_token&refresh_token=<refresh_token>' ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/oauth2/v1/ token -d 'grant_type=refresh_token&refresh_token=AQAgY2MzNjVlOTVhOTRh...vM5S0Mk rFSpzc=' Prerequisites for OAuth Client Credentials Perform the following tasks.Validate the Oracle Utilities application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Client Credentials for Allowed Grant Types is enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.4.Add the appropriate user(s) to the various Oracle Utilities application roles.For standard/production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)Chapter 2 Authentication Support 2-115.To assign the user, go to the Application Roles section of the application under AppWebServices .Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application API with an OAuth Utilities Connection.The application is added as a confidential application.2.Complete the Details section, and go to the Client section. |
curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token, use the refresh token and make a request to Oracle Identity Cloud Service.5.Capture the access_token and refresh_token from the response for further use.curl -i -H 'Authorization: Basic <base64-clientid-secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=refresh_token&refresh_token=<refresh_token>' ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/oauth2/v1/ token -d 'grant_type=refresh_token&refresh_token=AQAgY2MzNjVlOTVhOTRh...vM5S0Mk rFSpzc=' Prerequisites for OAuth Client Credentials Perform the following tasks.Validate the Oracle Utilities application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Client Credentials for Allowed Grant Types is enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.4.Add the appropriate user(s) to the various Oracle Utilities application roles.For standard/production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)Chapter 2 Authentication Support 2-115.To assign the user, go to the Application Roles section of the application under AppWebServices .Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application API with an OAuth Utilities Connection.The application is added as a confidential application.2.Complete the Details section, and go to the Client section.3.On the Client page, select Configure this application as a client now , and complete the following: a.Select Client Credentials from the Allowed Grant Types list. |
5.Capture the access_token and refresh_token from the response for further use.curl -i -H 'Authorization: Basic <base64-clientid-secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=refresh_token&refresh_token=<refresh_token>' ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/oauth2/v1/ token -d 'grant_type=refresh_token&refresh_token=AQAgY2MzNjVlOTVhOTRh...vM5S0Mk rFSpzc=' Prerequisites for OAuth Client Credentials Perform the following tasks.Validate the Oracle Utilities application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Client Credentials for Allowed Grant Types is enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.4.Add the appropriate user(s) to the various Oracle Utilities application roles.For standard/production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)Chapter 2 Authentication Support 2-115.To assign the user, go to the Application Roles section of the application under AppWebServices .Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application API with an OAuth Utilities Connection.The application is added as a confidential application.2.Complete the Details section, and go to the Client section.3.On the Client page, select Configure this application as a client now , and complete the following: a.Select Client Credentials from the Allowed Grant Types list.b.Select Specific in the Authorized Resources area of the Token Issuance Policy section. |
curl -i -H 'Authorization: Basic <base64-clientid-secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=refresh_token&refresh_token=<refresh_token>' ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/oauth2/v1/ token -d 'grant_type=refresh_token&refresh_token=AQAgY2MzNjVlOTVhOTRh...vM5S0Mk rFSpzc=' Prerequisites for OAuth Client Credentials Perform the following tasks.Validate the Oracle Utilities application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Client Credentials for Allowed Grant Types is enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.4.Add the appropriate user(s) to the various Oracle Utilities application roles.For standard/production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)Chapter 2 Authentication Support 2-115.To assign the user, go to the Application Roles section of the application under AppWebServices .Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application API with an OAuth Utilities Connection.The application is added as a confidential application.2.Complete the Details section, and go to the Client section.3.On the Client page, select Configure this application as a client now , and complete the following: a.Select Client Credentials from the Allowed Grant Types list.b.Select Specific in the Authorized Resources area of the Token Issuance Policy section.c.Click Add Scope under the Resources section. |
Validate the Oracle Utilities application and user roles: 1.Go to Configuration , and then Client Configuration of the Oracle Identity Cloud Service application.2.Verify that Client Credentials for Allowed Grant Types is enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.4.Add the appropriate user(s) to the various Oracle Utilities application roles.For standard/production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)Chapter 2 Authentication Support 2-115.To assign the user, go to the Application Roles section of the application under AppWebServices .Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application API with an OAuth Utilities Connection.The application is added as a confidential application.2.Complete the Details section, and go to the Client section.3.On the Client page, select Configure this application as a client now , and complete the following: a.Select Client Credentials from the Allowed Grant Types list.b.Select Specific in the Authorized Resources area of the Token Issuance Policy section.c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application. |
2.Verify that Client Credentials for Allowed Grant Types is enabled.3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.4.Add the appropriate user(s) to the various Oracle Utilities application roles.For standard/production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)Chapter 2 Authentication Support 2-115.To assign the user, go to the Application Roles section of the application under AppWebServices .Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application API with an OAuth Utilities Connection.The application is added as a confidential application.2.Complete the Details section, and go to the Client section.3.On the Client page, select Configure this application as a client now , and complete the following: a.Select Client Credentials from the Allowed Grant Types list.b.Select Specific in the Authorized Resources area of the Token Issuance Policy section.c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST or SOAP APIs or both REST and SOAP APIs, and click >. |
3.Go to Configuration , and then Resources of the Oracle Identity Cloud Service application.The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.4.Add the appropriate user(s) to the various Oracle Utilities application roles.For standard/production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)Chapter 2 Authentication Support 2-115.To assign the user, go to the Application Roles section of the application under AppWebServices .Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application API with an OAuth Utilities Connection.The application is added as a confidential application.2.Complete the Details section, and go to the Client section.3.On the Client page, select Configure this application as a client now , and complete the following: a.Select Client Credentials from the Allowed Grant Types list.b.Select Specific in the Authorized Resources area of the Token Issuance Policy section.c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST or SOAP APIs or both REST and SOAP APIs, and click >.Chapter 2 Authentication Support 2-12 f.Save your changes. |
The scope with access to either REST or SOAP APIs or both REST and SOAP APIs is provided.4.Add the appropriate user(s) to the various Oracle Utilities application roles.For standard/production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)Chapter 2 Authentication Support 2-115.To assign the user, go to the Application Roles section of the application under AppWebServices .Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application API with an OAuth Utilities Connection.The application is added as a confidential application.2.Complete the Details section, and go to the Client section.3.On the Client page, select Configure this application as a client now , and complete the following: a.Select Client Credentials from the Allowed Grant Types list.b.Select Specific in the Authorized Resources area of the Token Issuance Policy section.c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST or SOAP APIs or both REST and SOAP APIs, and click >.Chapter 2 Authentication Support 2-12 f.Save your changes.4.Click through the remaining wizard pages without making changes and save the application. |
4.Add the appropriate user(s) to the various Oracle Utilities application roles.For standard/production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)Chapter 2 Authentication Support 2-115.To assign the user, go to the Application Roles section of the application under AppWebServices .Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application API with an OAuth Utilities Connection.The application is added as a confidential application.2.Complete the Details section, and go to the Client section.3.On the Client page, select Configure this application as a client now , and complete the following: a.Select Client Credentials from the Allowed Grant Types list.b.Select Specific in the Authorized Resources area of the Token Issuance Policy section.c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST or SOAP APIs or both REST and SOAP APIs, and click >.Chapter 2 Authentication Support 2-12 f.Save your changes.4.Click through the remaining wizard pages without making changes and save the application.5.Activate the application for use. |
For standard/production configurations, use the ServiceUser role.(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)Chapter 2 Authentication Support 2-115.To assign the user, go to the Application Roles section of the application under AppWebServices .Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application API with an OAuth Utilities Connection.The application is added as a confidential application.2.Complete the Details section, and go to the Client section.3.On the Client page, select Configure this application as a client now , and complete the following: a.Select Client Credentials from the Allowed Grant Types list.b.Select Specific in the Authorized Resources area of the Token Issuance Policy section.c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST or SOAP APIs or both REST and SOAP APIs, and click >.Chapter 2 Authentication Support 2-12 f.Save your changes.4.Click through the remaining wizard pages without making changes and save the application.5.Activate the application for use.The next step is to create an application user in the appropriate Oracle Utilities Cloud Service (such as Oracle Utilities Meter Solution Cloud Service). |
(See Oracle Integration Service Roles in Provisioning and Administering Oracle Integration Generation 2 .)Chapter 2 Authentication Support 2-115.To assign the user, go to the Application Roles section of the application under AppWebServices .Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application API with an OAuth Utilities Connection.The application is added as a confidential application.2.Complete the Details section, and go to the Client section.3.On the Client page, select Configure this application as a client now , and complete the following: a.Select Client Credentials from the Allowed Grant Types list.b.Select Specific in the Authorized Resources area of the Token Issuance Policy section.c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST or SOAP APIs or both REST and SOAP APIs, and click >.Chapter 2 Authentication Support 2-12 f.Save your changes.4.Click through the remaining wizard pages without making changes and save the application.5.Activate the application for use.The next step is to create an application user in the appropriate Oracle Utilities Cloud Service (such as Oracle Utilities Meter Solution Cloud Service).Access the appropriate Oracle Utilities Cloud Service application, and navigate to the User portal. |
)Chapter 2 Authentication Support 2-115.To assign the user, go to the Application Roles section of the application under AppWebServices .Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application API with an OAuth Utilities Connection.The application is added as a confidential application.2.Complete the Details section, and go to the Client section.3.On the Client page, select Configure this application as a client now , and complete the following: a.Select Client Credentials from the Allowed Grant Types list.b.Select Specific in the Authorized Resources area of the Token Issuance Policy section.c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST or SOAP APIs or both REST and SOAP APIs, and click >.Chapter 2 Authentication Support 2-12 f.Save your changes.4.Click through the remaining wizard pages without making changes and save the application.5.Activate the application for use.The next step is to create an application user in the appropriate Oracle Utilities Cloud Service (such as Oracle Utilities Meter Solution Cloud Service).Access the appropriate Oracle Utilities Cloud Service application, and navigate to the User portal.1.Create a new user corresponding to the OAuth Client created above: a.Enter the OAuth client ID as the users login ID. |
Configure the client application: 1.In the Oracle Identity Cloud Service Console, go to the Applications section to create a new application that allows you to invoke an Oracle Utilities application API with an OAuth Utilities Connection.The application is added as a confidential application.2.Complete the Details section, and go to the Client section.3.On the Client page, select Configure this application as a client now , and complete the following: a.Select Client Credentials from the Allowed Grant Types list.b.Select Specific in the Authorized Resources area of the Token Issuance Policy section.c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST or SOAP APIs or both REST and SOAP APIs, and click >.Chapter 2 Authentication Support 2-12 f.Save your changes.4.Click through the remaining wizard pages without making changes and save the application.5.Activate the application for use.The next step is to create an application user in the appropriate Oracle Utilities Cloud Service (such as Oracle Utilities Meter Solution Cloud Service).Access the appropriate Oracle Utilities Cloud Service application, and navigate to the User portal.1.Create a new user corresponding to the OAuth Client created above: a.Enter the OAuth client ID as the users login ID.b.Select OAuth Client from the User Type drop-down list. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.