How To's

May 24, 2019 Steffo Weber

In this article, we’ll show you how to create your own SNS messaging service and connect it to Apple Push Notification Service (APNS) and Google Cloud Messaging (GCM). You will: 

    Set up AWS SNS Create a keypair Create a project for GCM services Create an SNS messaging…
May 24, 2019 Jonathan Knight

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: 

May 08, 2019 Stéphane Orluc

Integrating the ForgeRock Identity Platform With Prometheus and Grafana

April 26, 2019 Konstantin Lapine

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

April 26, 2019 Simon Moffatt

Handling authentication session life cycle notification in AM.

April 26, 2019 Leonard Moustacchis

Using AM to auto-provision an authentication tree.

March 20, 2019 Mark Craig

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

March 20, 2019 Mark Craig

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

March 20, 2019 Mark Craig

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

March 18, 2019 Marek Detko

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.