i4h5r (i4h5r) asked a question.
Hello, I have a question about the service. We want to allow third-party users to log in to our service through the login button. These users will be from other tenants of the okta. As far as I understand, I need to create OCID app and publish it via OIN, right? If yes I do not understand what should I add to the customer integration guide. this is just a button on my login page that user need to press
Hello @i4h5r (i4h5r) Thank you for reacting out to our Community!
You do not need to add the application to OIN, you can just create an Inbound SAML connection between the 2 Okta Orgs and the users can login though SAML. Please see the doc below on how to achieve this:
https://help.okta.com/en-us/content/topics/security/idp-inbound-saml-workflow.htm
--
Thanks for the reply. In case I need several organizations to log in to our service, it is better to publish SAML integration application. Am I right?
I have added a "SAML 2.0 IdP" in my organization. However, when a user from another organization tries to log in, an error occurs that he cannot log in.
Also I tried to add "OIDC - OpenID Connect" identity provider for OIDC application in my organization. I followed this guide https://developer.okta.com/docs/guides/add-an-external-idp/oktatookta/main/ . But when a user from another organization logs in, the same error appears that the user cannot log in.
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
May Okta Community Buzz
Stay ahead of the curve with Okta for AI Agents, new Okta Learning live sessions and labs, shout-outs, and top trending topics—all aimed at enriching your Okta journey.
Hello @i4h5r (i4h5r) Thank you for reacting out to our Community!
You do not need to add the application to OIN, you can just create an Inbound SAML connection between the 2 Okta Orgs and the users can login though SAML. Please see the doc below on how to achieve this:
https://help.okta.com/en-us/content/topics/security/idp-inbound-saml-workflow.htm
--
Subscribe Today: The Okta Community is on YouTube