Using API Portal 10.3 | API Portal Administrator's Guide | Managing API Assets | API Portal Extension Points
 
API Portal Extension Points
 
Managing Third-party Key Management Providers
Managing Access Tokens
Starting from 9.12 version, API Portal works as a standalone product where any third-party provider can be integrated as a key management provider. The third-party key provider should register as a provider in API Portal. You can publish a protected API and link it with the provider.
When a user sends the requests such as new key request, renew request or revoke request, the requests are stored in a local database in an events table with the status as NEW in API Portal. If the third-party provider is configured with the Push mechanism, the request is immediately sent to the provider and the status is changed to INPROGRESS in the events table. If the third-party provider is configured with Pull mechanism, then it starts querying events that have the status as NEW from the events table in API Portal. Once the event receipt is acknowledged by third-party provider, the status is changed to INPROGRESS in events table. Once the third-party provider processes the request and the success response is sent back to API Portal, the status changes to COMPLETED in the events table. In case the request is rejected, then the status is updated as REJECTED.

Copyright © 2014- 2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.