> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/writebackextreme/troubleshooting-and-faq/extension-errors/single-sign-on-saml/username-casing-in-idp-does-not-match-the-casing-in-tableau.md).

# Username casing in IDP does not match the casing in tableau

WriteBackExtreme verifies the username from the SSO provider with the username property of the user. When the casing is different (e.g. IDP returns <My.User@yourdomain.com> and the username in WriteBackExtreme is set to <my.user@yourdomain.com>) it will fail authorisation.&#x20;

This needs to be fixed on the IDP side. All major IDP providers have a way of transforming properties for SAML requests.&#x20;

* In [Azure](https://learn.microsoft.com/en-us/entra/identity-platform/saml-claims-customization#special-claims-transformations) for example you can add a transformation claim.&#x20;
* In Okta you can use [Okta expression language](https://developer.okta.com/docs/reference/okta-expression-language-in-identity-engine/) in the Attribute Statements like this: toLowerCase(user.email)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.infotopics.com/writebackextreme/troubleshooting-and-faq/extension-errors/single-sign-on-saml/username-casing-in-idp-does-not-match-the-casing-in-tableau.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.