Hi Jakub G.
Mind we did not use Okta, so I cannot tell you about this special config. I can only tell you where we had issues. And to be fair: we had multiple issues: First we had the settings not configured correctly and then the API token was misconfigured as well.
So make sure the Catalog Settings are enabled first. You can find them in wsONE here: Groups&Settings > Configurations => Here type ' Intelligent Hub' into the search field. Click on the resulting ' Intelligent Hub' .
There check under Catalog Settings that Hub Catalog is enabled.
You do also find this settings if you open Settings > Apps > Workspace ONE > AitWatchCatalog > General and select Tab ' Publishing' . Now you'll see Plattforms and some sliders. Toggle the ones you need. Usually, this should do the trick.
If not, there seems to be more screwed. In our case, the API connector.
So we had the issue of an incorrectly set up connector API that made it even more fun. I don't suppose this affects you as well, but for good measure, here's what we had to do:
The issue there was a misconfigured old API token which connects wsONE and vIDM. We had to contact wsONE Support to find out, that simply removing the old connection between wsONE and vIDM doesn't remove all certificates and tokes in the background. Yeah sure, would have been to easy anyway... So we did:
1. Make sure you have a local admin, not a AD admin or something alike. You'll need direct access and authentication. Make sure the same user exists in wsONE AND vIDM with the same credetials.
2. Remove the old connection, configuration and API from vIDM and wsONE
3. Reconfigure from scratch the vIDM & wsONE API call
=> Now you should be able to start the intelligentHub.
IF you meddle with the API, make sure you do everything on the correct level.
Hope this helps you somehow.
Best regards and good luck. If everything fails, contact the support. Really did the trick for us and saved us a lot of time.
