WSO2 is now Choreo LabsLearn more

Trusted AI Governance
Build

Create agents and AI apps with the tools and languages your teams already use.

Connect

Link agents securely to your APIs, data, models and business systems.

Run

Deploy, observe and operate agents and AI apps reliably at any scale.

Govern

Control identity, access, cost and policy for every agent in production.

Agent Management

Developer Platform

  • API Management Cloud

    Design, secure and publish APIs with governance and analytics built in.

    Sign Up Now
  • Integration Cloud

    Connect apps, data and AI agents with low-code and pro-code integration.

    Sign Up Now
  • Identity & Access Management Cloud

    Secure sign-in and access for customers, partners, workforce and agents.

    Sign Up Now
  • Agent Management Cloud

    Build, run and govern AI agents with full visibility and control.

    Sign Up Now
  • Developer Platform Cloud

    Ship cloud-native apps faster on an internal developer platform.

    Sign Up Now

Self-Hosted

Full control over your stack. Deploy directly to your own servers, bare metal, cloud, or Kubernetes environment. Your data never leaves your perimeter.

Product Downloads
Choreo Labs
AI Governance
Platform
Solutions
Resources
Article

[Blog post] OAuth for application developer and application user

OAuth has a well defined model to handle the API security using tokens, but how to use it with app development is not clear for most app developers as well as architects and technical managers who lead API solutions. That motivated me to write this blog post to make sure OAuth principles are utilized correctly in app development.

StubHub (who uses WSO2 API Manager to expose their business APIs) documented the security model for app development but I thought of simplifying for the benefit of the reader.

Subscription:

First the app-developer will register as a user and login to the api-store, the registry that list the APIs. Then he will register the app and subscribe for the APIs required for his development. As a result app-developer will get an access-token, consumer-key, consumer-secret. App-developer consumes the APIs during the development/test phase by using the consumer-key and re-request for new access-tokens by using consumer-key, consumer-secret and his credentials.

App development:

App-developer will embed the application key and application token in the app or in a configuration file of the app.

Once the development and testing of the app is done, the app-developer will publish the app in a store (public/private store based on the nature of the app), end-users of the app will download/access the app from store. Lets refer to the end-user as the app-user.

App usage:

App-user will register in the app user-store, and then request for a new access-token using the embedded consumer-key, consumer-secret and app-user credentials. The app-user's subscription similar to what the app-developer subscribed to using the consumer-key and consumer-secret.

In summary once an app-user registers in the user-store they can request for an access-token without a new subscription by using existing consumer-key, consumer-secret and app-user credentials.

Refer to Asanka's blog.