SushilB.32466 (Customer) asked a question.
How to Build new connection for netsuit app. as i am unable to see the netsuit app in new connection. I would like to build workflow for the new hires, for which netsuit app would be assigned on thir hire date.
Could you please share steps to create workflow for netsuit app
@SushilB.32466 (Customer) - The Okta Workflows product (Workflow > Workflows console) does not have built-in connectors for every possible third-party application. It does however provide options for connecting to and leveraging most third-party RESTful API's by either leveraging the API Connector card or the Connector Builder product (where you build your own connector for a third-party).
In either instance for the process to function you would need to first locate the vendor's API Documentation and determine the method(s) they require to perform Authn to gain access to the API. You would then need to perform the steps outlined in their documentation to generate their Access token and then buildout the requests to the endpoints.
However, if the vendor supports SCIM and you can natively setup provisioning in Okta Core (The Okta Admin UI) an alternative route may be just assigning the user to the application inside Okta and letting your SCIM integration do the provisioning. Inline with the rest of the above information this will still require research and testing on your end.
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
May Okta Community Buzz
Stay ahead of the curve with Okta for AI Agents, new Okta Learning live sessions and labs, shout-outs, and top trending topics—all aimed at enriching your Okta journey.
@SushilB.32466 (Customer) - The Okta Workflows product (Workflow > Workflows console) does not have built-in connectors for every possible third-party application. It does however provide options for connecting to and leveraging most third-party RESTful API's by either leveraging the API Connector card or the Connector Builder product (where you build your own connector for a third-party).
In either instance for the process to function you would need to first locate the vendor's API Documentation and determine the method(s) they require to perform Authn to gain access to the API. You would then need to perform the steps outlined in their documentation to generate their Access token and then buildout the requests to the endpoints.
However, if the vendor supports SCIM and you can natively setup provisioning in Okta Core (The Okta Admin UI) an alternative route may be just assigning the user to the application inside Okta and letting your SCIM integration do the provisioning. Inline with the rest of the above information this will still require research and testing on your end.