Okta "On - Premises" SCIM Provisioning to Cloud Service from OAN App-to-Be -


i developing integration between our cloud service , okta's idp. become official oan app end-users can install via okta interface. during development phase of project, using okta developer preview account. our app accepts provisioning traffic via scim rest apis exposes. okta tells don't support sending scim directly production application integration-partner scim servers, , tells way connect scim traffic our application use downloadable on-premises provisioning java connector. have installed connector on centos machine , connected our preview account, working , sending scim messages expected.

so, here's problem: when setting on-premises provisioning connector, had associate connector our specific okta preview account via configuration file, , accepting , associating via okta admin ui. plan put out application okta application network, each end-user provided unique key parameterized in application configuration , used component of scim base url each installation of our okta oan app. have 1 on-premises provisioning connector, , seems have point @ specific okta account, , impractical set separate on-premises provisioning connector daemon each of our many customer accounts. how supposed scim traffic each customer's oan apps , respective okta accounts?

it way easier if okta send scim directly. or, wonder if write our own "on-premises provisioning connector" somehow, don't know protocol speaks @ other end. thanks!

will: don't have enough reputation comment on question. please in touch okta account team. okta has un-released features address exact situation.


Comments

Popular posts from this blog

c# - Better 64-bit byte array hash -

webrtc - Which ICE candidate am I using and why? -

php - Zend Framework / Skeleton-Application / Composer install issue -