Skip to content

Instantly share code, notes, and snippets.

View yumingcao-okta's full-sized avatar

Yuming Cao yumingcao-okta

  • Okta
  • San Francisco
View GitHub Profile

Provisioning API

Design Doc: https://oktawiki.atlassian.net/wiki/display/eng/Provisioning+API+Design

Highlights:

  • Feature enabling & disabling operations are under [lifecycle endpoints] (#provisioning-lifecycle-operations)
  • Continue using Features object to indicate the status of provisioning features, enabled features will show in Features list
  • Use same Feature enums for lifecycle
  • 4 states ("DISABLED", "ENABLED", "NOT_AUTHORIZED", "NOT_SUPPORTED") for [provisioning status] (#provisioning-status-state-machine)
@yumingcao-okta
yumingcao-okta / app-keystore.md
Last active December 10, 2015 21:17 — forked from karlmcguinness-okta/app-keystore.md
Application KeyStore and Key Rollover

Application KeyStore and Key Rollover

This is the spec for key rollover feature phase 1 MVP, based on https://gist.github.com/karlmcguinness-okta/4d1b743a949cdd937e16

Diff compared to original spec:

  • no id, lastUpdated, e, n attributes for keys
  • expose x5t#S256 instead of x5t in JWK representation
  • update key endpoint accept PUT(full update) instead of POST(partial update)
  • no keyRollover convinence method