# If okta support cross org/domain management

**URL:** <https://devforum.okta.com/t/if-okta-support-cross-org-domain-management/21951>\
**Category:** Questions\
**Created:** [September 22, 2022, 9:05am UTC](https://devforum.okta.com/t/if-okta-support-cross-org-domain-management/21951 "2022-09-22T09:05:12Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![app](https://avatars.discourse-cdn.com/v4/letter/a/db5fbb/32.png) [@app](https://devforum.okta.com/u/app)\
**Post date:** [September 22, 2022, 9:05am UTC](https://devforum.okta.com/t/if-okta-support-cross-org-domain-management/21951/1 "2022-09-22T09:05:12Z")

</div>

I want to check with team if okta support below scenario

1. Both orgA([orgA.okata.com](http://orgA.okata.com)) and orgB([orgB.okata.com](http://orgB.okata.com)) are okta customers
2. **B is A’s customer**. A has App in Okta App Catalog like Salesforce, Autodesk Cisco Webex. **That’s support synchronize B’s users/groups in Okta to orgA by SCIM protocol.**

As I know orgB admin can manually  
create SCIM app  
Or create OAuth client and share client id/secret or provide API Key to others services. Others can create SCIM App and assign users/groups to App if scopes granted

But what i want is  
**Precondition: No SCIM App , OAuth client or API key configured in OrgB**  
3. B authorize A to manage its apps, users… e.g  
3.1 A open Okta’s authorization page require some privileges like app management  
3.2 orgB admin input username and password in the page  
3.3 orgB admin confirm authorization  
4. A authorized by B  
5. A can create OAuth client , SCIM App under orgB([orgB.okata.com](http://orgB.okata.com)) . **So orgB admin doesn’t need to do these things manually**

If it supported??

---

<div class="post-metadata">

**Author:** ![erik](https://avatars.discourse-cdn.com/v4/letter/e/b5ac83/32.png) [@erik](https://devforum.okta.com/u/erik)\
**Post date:** [September 22, 2022, 11:20pm UTC](https://devforum.okta.com/t/if-okta-support-cross-org-domain-management/21951/2 "2022-09-22T23:20:15Z")

</div>

It sounds like what you are describing is pretty close to OAuth for Okta,

> **[Implement OAuth for Okta | Okta Developer](https://developer.okta.com/docs/guides/implement-oauth-for-okta/main/)**
>
> Secure, scalable, and highly available authentication and user management for any app.

---

<div class="post-metadata">

**Author:** ![app](https://avatars.discourse-cdn.com/v4/letter/a/db5fbb/32.png) [@app](https://devforum.okta.com/u/app)\
**Post date:** [September 23, 2022, 2:05am UTC](https://devforum.okta.com/t/if-okta-support-cross-org-domain-management/21951/3 "2022-09-23T02:05:30Z")

</div>

The scenario in the doc is B create the OAuth client and share client the A **manually**  
But what i want is A create the client for B automatically after authorized by B.  
The authorization process is like i describe  
3.1 A open **Okta’s authorization page** require some privileges like app management  
3.2 orgB admin input username and password in the page  
3.3 orgB admin confirm authorization

OrgA get access token with OAuth and access orgB resource  
Normal Case (supported already)  
orgA page or service send request  
Get https://{orgB\_domian}/oauth2/v1/authorize? **client\_id=client\_provided\_by\_B** &scope=…

Post https://{orgB\_domian}/oauth2/v1/token **with above client after OrgB admin input username & password in page**

Expected  
orgA page or service send request by A’s client Id  
Get https://{orgB\_domian}/oauth2/v1/authorize? **client\_id=client\_from\_A** &scope=…  
**OrgB admin input username & password and confirm authorization**  
Then orgA send request  
Post https://{orgB\_domian}/oauth2/v1/token with **client\_id=client\_from\_A**

**Basically，A access B‘s resource using A’s own client after B authorized to A’s client**

---

<div class="post-metadata">

**Author:** ![andrea](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/andrea/32/2172_2.png) [@andrea](https://devforum.okta.com/u/andrea)\
**Post date:** [February 12, 2024, 10:05pm UTC](https://devforum.okta.com/t/if-okta-support-cross-org-domain-management/21951/4 "2024-02-12T22:05:13Z")

</div>

Closed on February 12, 2024, 10:05pm UTC


