<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
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D50Z00008C3jYdSAJOkta Classic EngineSingle Sign-OnAnswered2024-04-30T09:18:24.000Z2017-05-16T14:09:19.000Z2017-05-17T16:56:12.000Z

j5v7c (j5v7c) asked a question.

Edited by varun.kavoori1.5210444522562532E12 September 5, 2018 at 1:19 AM
Custom Egnyte Application URL
Hi, 

 

We've got Egnyte working using Okta SAML SSO. However we want to change the Egnyte URL that Okta has set-up...

 

When going through the set-up of Egnyte it asks for the customers domain, such as "exampledomain" if the url for Egnyte is https://exampledomain.egnyte.com

 

Whilst this works and everyone can sign-on, it's confusing for our users, - as we have a custom "Vanity URL" with Egnyte. For example: https://egnyte.exampledomain.com

 

I was wondering how I can get Okta to ensure the user lands on this Egnyte Vanity URL (https://egnyte.exampledomain.com) and not the one hardcoded in the Okta Egnyte app set-up (https://exampledomain.egnyte.com)?

 

Hope this all makes sense?

 

Thanks, 

 

John

 

  • 2 answers
  • 760 views

  • taylor.wells1.4885773203199763E12 (Okta, Inc.)

    The Default Relay State is the page users land on after a successful SAML login. You can try setting this to the URL you want users to be sent to when logging in. It can be edited on the Sign On tab of your Egnyte app. 

    0EM2A000000cAuy

  • 1fq50 (1fq50)

    I've tried this approach, but it doesn't work as far as I can tell.

     

    When using Default Relay State, we get the followin error upon sign in:

    Failed : Error Message - {error_message= Error occurred while parsing relay data 'https://custom.domain'}

    where custom.domain is our vanity URL.

     

    We'd also like a soltion to this. Wouldn't it be possible to allow the "Your Egnyte sub domain" field on the General tab to allow for a FQDN instead of it tacking on a .egnyte.com at the end?
    Expand Post
This question is closed.
Loading
Custom Egnyte Application URL