<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D50Z00008dk4YASAYOkta Classic EngineAdministrationAnswered2024-04-17T12:03:55.000Z2018-11-26T18:20:56.000Z2019-10-08T17:05:29.000Z
s6clx likes this.
  • Thank you for posting your question on the Okta Community. I would need more information on the location that you are using the login address and the error you receive. We would be able to better assist you if you could open a case with Okta Support. But in case you are referring to the length of the Login URL in the Application Integration Wizard, there is a hard limit of 255 characters in the login URL. The alternate solution to use longer URL's would be to Add a Template Application in Okta. Refer to the following documentation for further information about creating a Template Application in Okta: https://help.okta.com/en/prod/Content/Topics/Apps/Apps_Configure_Template_App.htm

    Expand Post
  • s6clx (s6clx)

    Is there a reason for the 255-limit, other than "Because that's our database field definition"? As more and more applications are using RESTFUL type interfaces, this becomes a real issue.

     

    For example, we use a company digikey account. The standard digikey login url from just clicking "log in" is more than 255 characters. So, we can do digikey integrations with Okta, and have to maintain separate users, logins, etc outside of it. I *could* probably do some template application or similar to make things happen, but shouldn't something as simple as a long url "just work"? Isn't that kind of the point of a service like this?

    Expand Post
This question is closed.
Loading
login address