Hi all, I have following the link [1] to do the oracle authenticator. For that I have follow the documentation [2] to install oracle identity and access management. Then only we can get the oracle access management console to Creating a Custom Resource Server and OAuth Client Registration. With the installation, I can access the oracle access management (OAM) console and create custom resource server and register the oauth clients as well.
When I try to get the authorization_code by using the endpoint which is mentioned in doc [3], I got the "401 unauthorized" error. I used 11GR2PS2 version while installing the oracle access and identity management, then I upgrade the version to 11GR2PS3. But I got the same response like unauthorized error for the two versions. [1] http://www.ateam-oracle.com/implementing-oauth-2-with-oracle-access-manager-oauth-services-part-i/ [2] http://docs.oracle.com/cd/E40329_01/install.1112/e49521/install.htm#INOAM75795 [3] http://www.ateam-oracle.com/implementing-oauth-2-with-oracle-access-manager-oauth-services-part-iii/ For the timing, Since I got the Token2 hardware token, I will move to the Token2 Authenticator(Hardware Token) as discussed in the mail thread [4]. Meanwhile I will check the possibility of continuing the Oracle Authenticator. [4] [Architecture] Token2 Provisioning connector and Authenticator for IS Thanks Kanapriya Kuleswararajan Associate Software Engineer Mobile : - 0774894438 Mail : - [email protected] On Thu, May 12, 2016 at 5:40 PM, Kanapriya Kuleswararajan < [email protected]> wrote: > Hi , > > I have planned to implement IS Authenticator for Oracle Access Manager. > > Oracle Access Manager is Oracle Identity Management's solution for web > access management and user identity administration. > > I have attached the flow diagram for $SUBJECT. > > > > 1. Accesses the Application. > 2. Authenticator request for authorization. > 3. Authenticate with Oauth Server. > 4. Returns Authorization code. > 5. Get the code from the response. > 6. Authenticator send the token request. > 7. Request for access Token. > 8. Sends the access Token. > 9. Get the token with the response. > 10. Send the request for user info. > 11. Pass the request to Resource server. > 12. Resource server send the request to Oauth server to validate the > token. > 13. Validates the Token. > 14. Grants the resources. > 15. Get the user info. > 16. Display the corresponding claims. > > > Thanks. > Kanapriya Kuleswararajan > Associate Software Engineer > Mobile : - 0774894438 > Mail : - [email protected] >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
