MAP.05794 (Customer) asked a question.
Hi guys, did you have a chance to create workflow in Okta which will show the result of Okta Import for example from HR system (please see the screenshot). I would like to send such a report in next step to dedicated channel in Slack.
@MAP.05794 (Customer) -- To the best of my knowledge there isn't an API available to either construct this information or generate and send a "report" of this information. Okta Workflows is only going to be able to Work with available public API's if they don't exist it doesn't have anything to interact with. There are quite a few different options/displays in the Okta Admin UI that leverage internal (private) API's and other more direct resource access to generate information that is not available through public API's.
I do see that there is a "view" for logs in the screenshot. This is likely going to be System Logs. If you look through the logs that it presents you should be able to determine if any of the events contain useful information that may "meet your needs". The System Log does have API Access and it would be possible to scrape events for data to build something. However, you would need to determine:
1) Is the data you need available in the events?
2) Is there an automated method for you to determine the relevant events and correlate them to a specific import job outside of the "Import Monitoring" UI. For example maybe they all have the same session ID. But how do you know it is the right "Import" and for which Directory? These events would need to be assessed to determine their usefulness.
If you are able to make positive determination and have figured out there is useful information and how to differentiate it then you could move on to automating the process via a Workflow.
@MAP.05794 (Customer) I was able to accomplish this for our HCM > Okta integration. It works really well. We spit it out to Slack so we get notified when the import is done and then get a nice clean summary. I'll work on putting it into a workflow and can attach it here.
@RossK.70107 (Customer) I would be really interested to see what you came up with. We have some issues where we're running into imports getting paused or having errors for various reasons and something like what you've described would be a great starting point.
Hey @Sean Wilson (Customer). This will vary depending on what system you're importing from, however, all of the data you're looking for is stored under the "system.import.user.complete" and "system.import.group.complete" eventTypes. You'll need a way to back into those events for the given import in question though, which is possibly easier than you might think it is. This is slightly different than how we have it implemented since I already have the session ID.
With that said, you should be able to create a workflow with an event trigger of "Import Started" and get the import session ID and then pass that along different sys log searches to ultimately arrive at the two eventTypes above.
Also, if you're trying to get ahead of failed imports, you could probably grab the sessionID, and inject a Wait For card to whatever your tolerance is, and then continue the flow. This way you won't have to pass/store values (like the sessionID) across different flows via a table or something along those lines. All of your imports would trigger the same flow, you could set If/else/if's for any special circumstances, and do its thing. I hope this helps but let me know if you have any questions.
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
@MAP.05794 (Customer) -- To the best of my knowledge there isn't an API available to either construct this information or generate and send a "report" of this information. Okta Workflows is only going to be able to Work with available public API's if they don't exist it doesn't have anything to interact with. There are quite a few different options/displays in the Okta Admin UI that leverage internal (private) API's and other more direct resource access to generate information that is not available through public API's.
I do see that there is a "view" for logs in the screenshot. This is likely going to be System Logs. If you look through the logs that it presents you should be able to determine if any of the events contain useful information that may "meet your needs". The System Log does have API Access and it would be possible to scrape events for data to build something. However, you would need to determine:
1) Is the data you need available in the events?
2) Is there an automated method for you to determine the relevant events and correlate them to a specific import job outside of the "Import Monitoring" UI. For example maybe they all have the same session ID. But how do you know it is the right "Import" and for which Directory? These events would need to be assessed to determine their usefulness.
If you are able to make positive determination and have figured out there is useful information and how to differentiate it then you could move on to automating the process via a Workflow.