> For the complete documentation index, see [llms.txt](https://docs.lenses.io/latest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lenses.io/latest/devx/5.5/deployment/configuration/iam/authentication/sso-and-saml/faqs.md).

# FAQs

### Authentication instances too old or in the future <a href="#id-1-authentication-instance-too-old-or-in-the-future" id="id-1-authentication-instance-too-old-or-in-the-future"></a>

#### The error that you see <a href="#the-error-that-you-see" id="the-error-that-you-see"></a>

```plaintext
Authentication issue instant is too old or in the future
```

#### What causes it <a href="#what-causes-it" id="what-causes-it"></a>

1. The user’s session in the SSO provider is too old.
2. The system clocks of the SSO provider and the Lenses instance are out of sync.

For security purposes, Lenses prevents authenticating SSO users that have remained logged in SSO for a very long time.

Example: You use Okta SSO and, you logged in to Okta a year ago. Okta might allow you to remain logged in along that year without having to re-authenticate. Lenses has a limit of `100 days`. In that case, Lenses will receive an authenticated user that originally logged in before the 100 days mark.

#### How to solve it <a href="#how-to-solve-it" id="how-to-solve-it"></a>

1. Ensure that the SSO and Lenses system clocks are in sync.
2. If the SSO provider supports very long sessions either:
   1. Log out of the SSO and log back in. This explicitly renews the SSO session.
   2. Increase the Lenses limit to more than `100 days`.

Example:

```properties
lenses.security.saml.idp.session.lifetime.max = 365days
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.lenses.io/latest/devx/5.5/deployment/configuration/iam/authentication/sso-and-saml/faqs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.