How To's

Instructions for creating a push authenticator app for your mobile phone to handle registration and authentication using AM push notification.

For more information about Push services in AM/OpenAM: https://backstage.forgerock.com/knowledge/kb/book/b12434442/cover 
 

Integrating the ForgeRock Identity Platform With Prometheus and Grafana

Building a generic OAuth 2.0 client with the AppAuth SDK for iOS.

Using AM to auto-provision an authentication tree.

Handling authentication session life cycle notification in AM.

Instructions for demonstrating a single-page app with OIDC-based SSO.

Instructions for demonstrating an OAuth 2.0 authorization code grant in a Vert.x App.

Instructions for demonstrating an OAuth 2.0 implicit grant in a web app. 

AM acts as an autorization server (AS) and Apigee is a Resource Server (RS).

All tokens are issued by AM. It doesn't matter which OAuth2 grant was used to issue token. However if you decide to use either client credentials or resource owner password grants, Apigee offers quite easy way of integrating those flows. Example of such integration can be found in Wayne's blog.

If you decide to use either authorization code or implicit grants, it is easier to issue token directly at external AS and just use the token to protect APIs at RS. If it is required to pass all requests through Apigee, then I suggest to proxy autorization and token endpoint to AS without trying to use any Apigee flows.

Instructions for trying the ForgeRock embedded login JavaScript library.