<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
ナビゲーションへスキップメインコンテンツへスキップ
0D50Z00008C3jklSABOkta Classic EngineLifecycle ManagementAnswered2026-04-18T09:02:08.000Z2017-11-30T22:14:30.000Z2017-11-30T22:14:30.000Z

925wn (925wn) さんが質問をしました。

Has anyone setup Okta Provisioning for their On Premises GitHut Enteprise application? IF so, did you use a SCIM connector or open up all the Okta AWS IP's to your on prem application or something else? Thanks!
Has anyone setup Okta Provisioning for their On Premises GitHut Enteprise application? IF so, did you use a SCIM connector or open up all the Okta AWS IP's to your on prem application or something else? Thanks!

  • Thank you for reaching out to Okta, my name is Bogdan.

    We would highly recommend opening whitelisting that range of AWS IP's for HTTPS requests from Okta.

    When provisioning is enabled and authenticating the API, one of our web servers in AWS will make a call to the Github endpoint.

    Given the fact that the AWS server that will be used is chosen randomy we recommend whitelisting that range of AWS IP's for HTTPS.

    For more information, see the following documentation: 

    https://support.okta.com/help/Documentation/Knowledge_Article/Configuring-Firewall-Whitelisting-89944588

     

    Thank you.
    投稿を展開
この質問は閉じられました。
読み込み中
Has anyone setup Okta Provisioning for their On Premises GitHut Enteprise application? IF so, did you use a SCIM connector or open up all the Okta AWS IP's to your on prem application or something else? Thanks!