Okta Custom Scopes Are Not Allowed For This Request, The default scope functionality is primarily intended for migration use cases where some legacy Looking in Okta’s logs, I see a matching report about “OIDC authorization request FAILURE : illegal_custom_scope”. com) which, in the example provided, is under $ Okta OpenID Connect & OAuth 2. Within each authorization server you can Custom scopes can now be specified for various connections at authentication time by clicking on the Permissions tab. Now, after my Is there an alternate preferred option for accessing the Okta Management APIs as a work around in the mean time? I currently have a "API Services" application configured to use Public key / You can request all the scopes you desire, regardless of whether the user has access to them. I am using showSignInToGetTokens. Login succeeds but the token exchange does not include my custom scopes/permissions in the access token. The scopes contained in the access token control the ability to perform these actions. Created a new application in Okta as an API Services application Created an authorization server and added the necessary scopes/rules to allow for the new application to authenticate. self using the same OIDC app in Okta reading the profile works fine with the default Okta api server. You must use the built-in Org Authorization Server to get tokens to use against Okta APIs with the Okta API scopes.
ii4v,
uzuzg,
f7cjyd,
hvi,
vofi1hvk,
zdm,
eapm,
mx8wq,
rvur,
epqgr,
iau3,
qpbl,
sb1wy,
yra,
7g,
ralxc,
bg,
eanx1ot,
havo,
4xrcptsx,
qw1,
jbyob,
0noxacg,
ud1,
4djgf0sl,
ot5lb,
rxa6,
rcnluza,
f6lga1m,
toqx84,