-
Suggestion
-
Resolution: Unresolved
-
Low
-
None
-
None
-
None
-
None
Issue Summary
There are times where an Atlassian product (Confluence, Jira) that is configured with SAML returns an authentication error even though authentication is successful. The following error is seen:
Typically this is normally caused by issues such as what is described here:
While the above is the most common cause of the issue, there are other situations that involves connections resets that causes this.
Although the end users are displayed the above error message, authentication is essentially successful. A simple refresh of the page or navigating anywhere within the product (Confluence for example) would be successful. The issue here is that it is very confusing for the end users who would think that something went wrong during authentication.
Request
Confluence should have either better error messaging to instruct users to reload the page, or there should be a built in verification process that checks whether the authentication was successful which would trigger an automatic reload of the page
[SAMLDC-129] Add an internal verification process when SAML authentication is successful
| Description |
Original:
h3. Issue Summary
There are times where Confluence returns an authentication error even though authentication is successful. The following error is seen: !Screenshot_2023-05-02_at_14_07_01-1.png|thumbnail! Typically this is normally caused by issues such as what is described here: * [Connection reset while Directory Sync with Jira due to longer keep-alive|https://confluence.atlassian.com/confkb/connection-reset-while-directory-sync-with-jira-due-to-longer-keep-alive-1031278471.html] While the above is the most common cause of the issue, there are other situations that involves connections resets that causes this. Although the end users are displayed the above error message, authentication is essentially successful. A simple refresh of the page or navigating anywhere in Confluence would be successful. The issue here is that it is very confusing for the end users who would think that something went wrong during authentication. h3. Request Confluence should have either better error messaging to instruct users to reload the page, or there should be a built in verification process that checks whether the authentication was successful which would trigger an automatic reload of the page |
New:
h3. Issue Summary
There are times where an Atlassian product (Confluence, Jira) that is configured with SAML returns an authentication error even though authentication is successful. The following error is seen: !Screenshot_2023-05-02_at_14_07_01-1.png|thumbnail! Typically this is normally caused by issues such as what is described here: * [Connection reset while Directory Sync with Jira due to longer keep-alive|https://confluence.atlassian.com/confkb/connection-reset-while-directory-sync-with-jira-due-to-longer-keep-alive-1031278471.html] While the above is the most common cause of the issue, there are other situations that involves connections resets that causes this. Although the end users are displayed the above error message, authentication is essentially successful. A simple refresh of the page or navigating anywhere within the product (Confluence for example) would be successful. The issue here is that it is very confusing for the end users who would think that something went wrong during authentication. h3. Request Confluence should have either better error messaging to instruct users to reload the page, or there should be a built in verification process that checks whether the authentication was successful which would trigger an automatic reload of the page |
| Description |
Original:
h3. Issue Summary
There are times where Confluence returns an authentication error even though authentication is successful. The following error is seen: !Screenshot_2023-05-02_at_14_07_01-1.png|thumbnail! Typically this is normally caused by issues such as what is described here: * [Connection reset while Directory Sync with Jira due to longer keep-alive|https://confluence.atlassian.com/confkb/connection-reset-while-directory-sync-with-jira-due-to-longer-keep-alive-1031278471.html] While the above is the most common cause of the issue, there are other situations that involves connections resets that causes this. Although the end users are displayed the above error message, authentication is essentially successful. A simple refresh of the page or navigating anywhere in Confluence would be successful. The issue here is that it is very confusing for the end users who would think that something went wrong during authentication. h3. Request Confluence should have either better error messaging to instruct users to reload the page, or there should be a built in verification process that checks whether the authentication was successful which would trigger an automatic reload of the page |
New:
h3. Issue Summary
There are times where Confluence returns an authentication error even though authentication is successful. The following error is seen: !Screenshot_2023-05-02_at_14_07_01-1.png|thumbnail! Typically this is normally caused by issues such as what is described here: * [Connection reset while Directory Sync with Jira due to longer keep-alive|https://confluence.atlassian.com/confkb/connection-reset-while-directory-sync-with-jira-due-to-longer-keep-alive-1031278471.html] While the above is the most common cause of the issue, there are other situations that involves connections resets that causes this. Although the end users are displayed the above error message, authentication is essentially successful. A simple refresh of the page or navigating anywhere in Confluence would be successful. The issue here is that it is very confusing for the end users who would think that something went wrong during authentication. h3. Request Confluence should have either better error messaging to instruct users to reload the page, or there should be a built in verification process that checks whether the authentication was successful which would trigger an automatic reload of the page |
| Component/s | Original: Server - Authentication [ 42866 ] | |
| Key | Original: CONFSERVER-83320 | New: SAMLDC-129 |
| QA Demo Status | Original: Not Done [ 14330 ] | |
| QA Kickoff Status | Original: Not Done [ 14234 ] | |
| Priority | New: Low [ 4 ] | |
| Project | Original: Confluence Server and Data Center [ 10470 ] | New: SAML for Atlassian Data Center [ 18310 ] |
| Description |
Original:
h3. Issue Summary
There are times where Confluence returns an authentication error even though authentication is successful. The following error is seen: !Screenshot_2023-05-02_at_14_07_01-1.png|thumbnail! Typically this is normally caused by issues such as what is described here: * [Connection reset while Directory Sync with Jira due to longer keep-alive|https://confluence.atlassian.com/confkb/connection-reset-while-directory-sync-with-jira-due-to-longer-keep-alive-1031278471.html] While the above is the most common cause of the issue, there are other situations that involves connections resets that causes this. Although end users are displayed the above error message, authentication is essentially is successful, a simple refresh of the page or navigating anywhere in Confluence would be successful. The issue here is that it is very confusing for the end users who would think that something went wrong. h3. Request Confluence should have either better error messaging to instruct users to reload the page, or there should be a built in verification process that checks whether the authentication was successful which would trigger an automatic reload of the page |
New:
h3. Issue Summary
There are times where Confluence returns an authentication error even though authentication is successful. The following error is seen: !Screenshot_2023-05-02_at_14_07_01-1.png|thumbnail! Typically this is normally caused by issues such as what is described here: * [Connection reset while Directory Sync with Jira due to longer keep-alive|https://confluence.atlassian.com/confkb/connection-reset-while-directory-sync-with-jira-due-to-longer-keep-alive-1031278471.html] While the above is the most common cause of the issue, there are other situations that involves connections resets that causes this. Although the end users are displayed the above error message, authentication is essentially successful. A simple refresh of the page or navigating anywhere in Confluence would be successful. The issue here is that it is very confusing for the end users who would think that something went wrong during authentication. h3. Request Confluence should have either better error messaging to instruct users to reload the page, or there should be a built in verification process that checks whether the authentication was successful which would trigger an automatic reload of the page |
| Summary | Original: Better error messaging when authentication is successful | New: Add an internal verification process when SAML authentication is successful |
| Description |
Original:
h3. Issue Summary
In situations where authentication is successful through SAML, there are times where Confluence returns an authentication error even though authentication is successful. The following is seen h3. Steps to Reproduce # Step 1 # Step 2 h3. Expected Results h3. Actual Results The below exception is thrown in the xxxxxxx.log file: {noformat} ... {noformat} h3. Workaround Required, if there is no workaround please state: Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
There are times where Confluence returns an authentication error even though authentication is successful. The following error is seen: !Screenshot_2023-05-02_at_14_07_01-1.png|thumbnail! Typically this is normally caused by issues such as what is described here: * [Connection reset while Directory Sync with Jira due to longer keep-alive|https://confluence.atlassian.com/confkb/connection-reset-while-directory-sync-with-jira-due-to-longer-keep-alive-1031278471.html] While the above is the most common cause of the issue, there are other situations that involves connections resets that causes this. Although end users are displayed the above error message, authentication is essentially is successful, a simple refresh of the page or navigating anywhere in Confluence would be successful. The issue here is that it is very confusing for the end users who would think that something went wrong. h3. Request Confluence should have either better error messaging to instruct users to reload the page, or there should be a built in verification process that checks whether the authentication was successful which would trigger an automatic reload of the page |
| Attachment | New: Screenshot_2023-05-02_at_14_07_01-1.png [ 437645 ] |