Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for OIDC activation type #619

Closed
hvge opened this issue Sep 12, 2024 · 0 comments
Closed

Support for OIDC activation type #619

hvge opened this issue Sep 12, 2024 · 0 comments
Assignees
Milestone

Comments

@hvge
Copy link
Member

hvge commented Sep 12, 2024

The new PowerAuth stack 1.9+ will directly support new OIDC activation type. This ticket is about to add this functionality to the mobile SDK. As a part of this change, we should deprecate all activation-related methods except method using PowerAuthActivation object at its input.


Required Changes

Reuse of Existing Custom Activation Type

There will be no new activation type for OIDC, there will be just a CUSTOM activation with specific implementation for OIDC.

As part of this functionality we will introduce DIRECT activation type, which will be an alias for CUSTOM activation type.

Let's call the custom activation type direct in this specification.

Direct Activation Type Parameters

Following parameters are used during OIDC activation:

  • method - oidc - to separate from other custom activations and enable default functionality in enrollment server
  • providerId - OAuth 2.0 provider identification
  • code - OAuth 2.0 authorization code
  • nonce - nonce used in the OAuth 2.0 flow

Direct Activation Request

{
  "type": "DIRECT",
  "identityAttributes": {
      "method": "oidc",
      "providerId": "1234567890abcdef",
      "code": "1234567890abcdef",
      "nonce": "K1mP3rT9bQ8lV6zN7sW2xY4dJ5oU0fA1gH29o"
  },
  "customAttributes": {
  },
  "activationData": "..."
}
@hvge hvge added this to the 1.9.0 milestone Sep 12, 2024
@hvge hvge self-assigned this Sep 12, 2024
@hvge hvge closed this as completed in 195cc1a Sep 18, 2024
hvge added a commit that referenced this issue Sep 18, 2024
kober32 added a commit that referenced this issue Sep 19, 2024
# Conflicts:
#	docs/Migration-from-1.8-to-1.9.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant