tmzxc (tmzxc) asked a question.
Hi support!
Our developers are complaining about the fact that they have to re-authorize in okta all the time when in github. Can something be done about this? Even if it's just extending this timeout to a week?
Thank you for posting your question on Okta Community. I would recommend you to open a case with Okta support to investigate the issue being faced. But generally speaking, the session for Github is not maintained by Okta. After you sign into the application, the application session time is maintained by Github. It will reach Okta for re authorization after the current session expires. You may be prompted to sign in to Okta if your Okta session expires based on your Session Lifetime set on your Okta sign on Policy under Security > Authentication. You can modify your session lifetime in your Okta Sign on policy to avoid signing into Okta each time for re authentication.
Hi Vignesh.
In the meantime I received an answer from Marius form Okta support. Turns out github is expecting a saml param called "SessionNotOnOrAfter" which okta is not sending based on the desired session duration. Marius suggested to ask for help / info here, but not sure where to go from here 🙂
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
Thank you for posting your question on Okta Community. I would recommend you to open a case with Okta support to investigate the issue being faced. But generally speaking, the session for Github is not maintained by Okta. After you sign into the application, the application session time is maintained by Github. It will reach Okta for re authorization after the current session expires. You may be prompted to sign in to Okta if your Okta session expires based on your Session Lifetime set on your Okta sign on Policy under Security > Authentication. You can modify your session lifetime in your Okta Sign on policy to avoid signing into Okta each time for re authentication.