Skip to content

A demo of an Event Listener plugin which publishes tokens to the Apigee Edge using the Split Token approach

License

Notifications You must be signed in to change notification settings

curityio/apigee-split-token-publisher

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Apigee Split Token Publisher Demo Plugin

Quality Availability

This is an example event listener SDK Plugin for the Curity Identity Server. The plugin registers an event listener listening for issued access token events, and forwards them to Apigee Edge cache, using the Split Token approach.

Building, installation and configuration

To build the plugin, simply download it and run mvn package. This creates target/identityserver.plugins.events.listeners.apigee-split-token-publisher-1.0.0.jar. Create a new folder apigee_split_token_publisher in <idsvr_home>/usr/share/plugins/ then copy the jar to that folder and (re)start the Curity Identity Server. Configure a new event listener (shown here using the Admin UI, but might just as well be configured through the CLI, REST or XML):

Add new listener

Pick a suitable name and then select the "apigee-split-token-publisher" type:

Select type

The Apigee token listener needs a http client configured for communication with Apigee Edge. Click the + Create button next to the Http Client dropdown and provide a name for the client:

Add new http client

Choose http-basic-authn as the HTTP Authentication mechanism and fill in the values for username and secret - these have to match the id and secret that will be set in Apigee flow receiving these requests.

Configure client

You can leave the rest of the options set to default. Click Create at the bottom of the form. Fill in the hostname of your Apigee Edge:

Configure the listener

Then Save and Commit the changes.

Please visit curity.io for more information about the Curity Identity Server.