StephenG.11459 (Customer) asked a question.
I am trying to configure Anything as a Source and the "Create Import Session" requires "okta.identitySources.manage" but when I go to add that in the Okta Workflows OAuth app the scope doesn't exist. I tried adding okta.idps.manage which seems to be the same but that still fails even after reauth saying it doesn't have permission.
Was the API Scope changed or am I missing something?
According to this page Guidance for Okta connector | Okta I should see it under the Workflows OAuth app but when I look there I only see:
@StephenG.11459 (Customer) -- This would indicate XaaS isn't enabled on your org. Keep in mind Workflows is just a client that can be leveraged with XaaS and isn't actually part of XaaS. Technically any client even your own custom created one could be leveraged as it just needs to be capable of authenticating and making REST API calls.
To enable XaaS in your environment please open a support case requesting the feature be enabled. Once the feature is enabled those scopes should be available on the Workflows Oauth app (or any other OIDC app you create).
For additional clarity / future reference. The article you previously linked is listing the subset of scopes the Workflows connector will request of the OIDC app it is connecting to (Okta Workflows Oauth). With Oauth that app needs to have those scopes enabled/available to be able to grant them. The reason I am mentioning this is there are other scopes not in that article's list you wouldn't be able to leverage the the Okta Connector to gain the grants needed. In those instances you would need to leverage a custom OIDC app. See:
Thanks @TimL.58332 (Workflows), I'll work with my account team to make sure all the feature flags are enabled. I had some of them enabled but will check with them.
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
@StephenG.11459 (Customer) -- This would indicate XaaS isn't enabled on your org. Keep in mind Workflows is just a client that can be leveraged with XaaS and isn't actually part of XaaS. Technically any client even your own custom created one could be leveraged as it just needs to be capable of authenticating and making REST API calls.
To enable XaaS in your environment please open a support case requesting the feature be enabled. Once the feature is enabled those scopes should be available on the Workflows Oauth app (or any other OIDC app you create).
For additional clarity / future reference. The article you previously linked is listing the subset of scopes the Workflows connector will request of the OIDC app it is connecting to (Okta Workflows Oauth). With Oauth that app needs to have those scopes enabled/available to be able to grant them. The reason I am mentioning this is there are other scopes not in that article's list you wouldn't be able to leverage the the Okta Connector to gain the grants needed. In those instances you would need to leverage a custom OIDC app. See:
https://support.okta.com/help/s/article/How-to-create-a-custom-OIDC-app-for-Workflows-that-includes-OAuth-scopes-not-supported-by-the-Okta-connector?language=en_US