<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
0D5WR00001Cf5N00AJOkta Classic EngineCustom URL DomainsAnswered2026-01-30T17:08:53.000Z2026-01-23T17:14:44.000Z2026-01-30T17:08:53.000Z
Cannot Configure Custom Brands - Okta constantly states Invalid Session or logs out

Previously had an Okta Dev account to test integrations between my product and Okta. Everything was fine there - after the move to Okta Trials for the same purpose - Okta has become virtually unusable.

 

Attempting to setup a custom login URL under Customizations > Brands. I can get to the screen where I put in a URL and immediately get an "Invalid Session" box that appears. If I click anywhere else to navigate to another site - I get prompted for my password and push message again.

 

In some cases I have made it to the next screen and get the info for my TXT file and CNAME - but even if I have two screens up I cannot go fast enough. I put the information in my DNS host and click next to get the same Invalid Session box.

 

If I refresh my login and try to continue the registration - immediately get "invalid session". If I try to move to take a look at my login policies I get 403 error and have to login again.

 

I had this in December and thought it might have been an issue with Okta and have had the issue twice more in trying to return to the platform. I have tried different networks and different computers.

 

As I have a trial account - I can't open a case for what, to me, looks like a tenant issue. Any ideas here? I need to test and make sure my app fully supports okta - but at this point I can't even change my logins.

 

Screenshot below - I got this within 15 seconds of logging in. If I click on a side bar item I have to re-auth.

 

Screenshot 2026-01-23 at 2.02.26 PM


  • Mihai N. (Okta, Inc.)

    Hi @PatrickM.02823 (Customer)​ , Thank you for reaching out to the Okta Community! 

     

    I recommend going through your Global access policies as well the Sign-on policies for the Okta Admin app to check if there is a misconfiguration that would cause the session to end early.

    There is also the "protected actions" feature to look into, but I don't think that comes into play here.  

    If you already have an app added to the Okta Integrations Network catalog, you can email our colleagues at developers@okta.com - subject line should include "ISV - <description of issue>". 

     

    Beyond that, my advice would be to sign up for a New Integrator Free Plan Sign up is free, using the method mentioned at step 2 in this article

     

     

    Regards.

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Collect them all. Learn a new skill and earn a new Okta Learning badge.

    Just released: More Okta Community badges just added

    Expand Post
    Selected as Best
  • PatrickM.02823 (Customer)

    This is not a Global access policy - this only happens when I try to setup custom branding and started around the new year. At this point I can't even get to other pages aside from the dashboard without getting 403 errors.

     

    Surely there is a better answer than "make a new account"? This is already my second okta instance after the EOL of the dev accounts. This is a functional issue with Okta, not just a problem from a silly policy. Whenever I can get to the branding pages to delete my custom branding - the problem goes away. Its only after introducing custom branding and we can't even complete the setup.

    Expand Post

Loading
Cannot Configure Custom Brands - Okta constantly states Invalid Session or logs out