/role-store/api/v1/identity-providersAsk AIpost https://example.com/role-store/api/v1/identity-providersCreate a new Identity Provider.Body Paramsiduuidnamestringrequiredlength between 2 and 2042Identity provider name, must be uniquetoken_typestringenumrequiredToken type. Only "JWT" is supported.JWTAllowed:JWTjwt_issuerstringrequiredlength ≤ 2042JWT issuerjwt_audiencestringlength ≤ 2042Expected JWT audience. JWT aud claim must either have a single matching value or it must be have an array of values of which at least one value must match.jwt_subject_typestringenumrequiredJWT subject claim formatplaindnAllowed:plaindnjwt_subject_dn_username_attributestringIf jwt_subject_type is "dn" then jwt_subject_dn_username_attribute specifies the name of the attribute to be used as username when resolving the usercustom_attributesarray of objectscustom_attributesADD objectpublic_key_methodstringenumMethod for obtaining the token verification public keystaticx5ux5u-publickeyAllowed:staticx5ux5u-publickeypublic_keysarray of objectspublic_keysADD objectx5u_trust_anchorstringTrust anchor for verifying X.509 certificates fetched from x5u urls. Required if public_key_method is "x5u"x5u_tls_trust_anchorstringTrust anchor for TLS server certificates used when fetching X.509 certificates or public keys from x5u urls. If not specified then system trust anchors will be used.x5u_prefixuriThe url in the token's x5u claim must start with the x5u_prefix or it will be rejected. x5u_prefix must be a valid https url. Required if public_key_method is "x5u-publickey".enabledbooleanEnable/Disable Identity Providertruefalseusers_directoryuuidrequiredID of the PrivX user directory from which the users are resolved by token's sub claim. OIDC user directories are not supported.authoruuidIdentity Provider Authorcreateddate-timeCreation timeupdateddate-timeTime of the last updateupdated_bystringID of the user who last updated the identity providerHeadersAuthorizationstringrequiredDefaults to Bearer a-proper-token-goes-hereOAuth2 tokenResponses 201Identity Provider Successfully created 400Bad request 401Unauthorized request, OAuth2 authorization missing or invalid 403Unauthorized request, OAuth2 authorization OK but scope insufficient 404Resource not found 500Internal server errorUpdated over 2 years ago