User16736442575841618508 (Customer) asked a question.
How to grant the okta.myAccount.password.manage scope to Application
I'm building a custom login app that uses the embedded widget. An additional requirement for this app is to build a change password page. I would like to use the MyAccount Management API using the Replace a Password operation to accomplish this feature. That API requires the okta.myAccount.password.manage scope, however I cannot figure out how to grant that scope to my application, it just isn't available. I'm a Super Admin within my Okta Organization and can make any necessary configuration changes to get this working. Anyone else out there run into a similar issue and know how to resolve this?
Forgot to include this in my question. This from the list of Okta API Scopes within my App configuration.
Hello @User16736442575841618508 (Customer) Thank you for reacting out to our Community!
Please see this documentation that should provide you with the required info:
https://developer.okta.com/docs/reference/api/myaccount/#get-my-password
Additionally if you need further assistance we recommend to leverage the Okta Developer forums for this type of questions and take advantage of their expertise.
https://devforum.okta.com/
Community members help others by clicking Like or Select as Best on responses. Try it today.
Thank you for the response Paul, however that is the documentation that I have been pouring over, unfortunately that documentation does not explain how to grant the okta.myAccount.password.manage scope. That scope appears to be non-existent within my Okta organization, so I assume it requires some sort of configuration within the Okta Admin portal to enable it. From my experience working with the Update My Password that scope should exist, the operation fails because my access token doesn't contain said scope, but when I make a token request containing that scope it also fails stating that the scope isn't configured for the authorization server resource. I cannot add this scope to the authorization server, because the system prevents custom scopes from starting with okta. I've tried spinning up a new development Okta organization so I could have Super Admin access, but haven't yet found any configuration that enables the scope to be granted. Thus I'm stuck.