"Login through URL" not working anymore?

[Roland Siegel]

Hi,

we updated to Confluence Server 7.12.5 and suddenly the "Login through URL" (see https://confluence.atlassian.com/confkb/confluence-url-list-317949394.html - "Special URLs" at the page bottom) doesn't work anymore.
We now get redirected to the login page. Before the update the same URL logged us in and showed the destination page correctly.

https://confluence.hup.de/pages/viewpage.action?pageId=15800417&os_username=USER&os_password=PASS

(values of os_username and os_password changed) ;-)

Does anyone has the same problem or did sth change within this function? Is the documentation still correct?

Thanks for any help!
It seems that Atlassian has abandoned any support, because they didn't react in any way to my question through the page feedback function for over 2 weeks.

Best Regards,
Roland

[Roland Siegel · Accepted solution]

Response from Atlassian:

This feature was turned of with Confluence 7.10

Have a look at "Login with query parameter no longer supported":
https://confluence.atlassian.com/doc/confluence-7-10-upgrade-notes-1026054305.html 

Atlassian promotes the login via personal access token as described in the article as well as a workaround to reenable the old login method via get parameters.

[Kishan Sharma]

Thank you for sharing here @Roland Siegel 

[Kishan Sharma]

Hi @Roland Siegel I have personally not attempted this before, but can you try below URL if it's working for you ? eg - change username/password as necessary -

https://confluence.hup.de/dashboard.action?os_username=USER&os_password=PASS

[Roland Siegel]

Hi @Kishan Sharma ,

I tried this as well and only get redirected to the System Dashboard but still not logged in.

When I try
https://confluence.hup.de/login.action?os_username=USER&os_password=PASS
I see that (only) my username is filled in the login dialogue, but here as well, no login process happens.

[Kishan Sharma]

Thanks Roland, its not working for me either on v7.4.0, not sure why. I would also suggest raising a support ticket with Atlassian Support directly for help.

[Kishan Sharma]

Please post here if you get solution from Atlassian Support.

[Roland Siegel]

Alright, I will report back, when Atlassian finds time to answer my unimportant problem. %-}

[Roland Siegel]

Hi @Kishan Sharma 

I got news from Atlassian.

With Confluence 7.10 this feature was turned off.

See "Login with query parameter no longer supported" on:
https://confluence.atlassian.com/doc/confluence-7-10-upgrade-notes-1026054305.html

Atlassian promotes the login via personal access token as described in the article as well as a workaround to reenable the old login method via get parameters.

[Kishan Sharma]

ah ok must be for a reason, thank you for sharing @Roland Siegel :)

[Rahul Jain]

@Kishan Sharma  did the workaround to use atlassian.allow.insecure.url.parameter.login worked for you.

I am using Atlassian Confluence 7.13.0 (Data Centre) and tried this work around but it didn't work.

[Kishan Sharma]

Hi @Rahul Jain No I have not tried it as I don't have that version to test.

[Rahul Jain]

Thanks for the quick reply @Kishan Sharma , but did you use the workaround provided, for your confluence version, or you implemented some diff. way to authenticate user.

@Roland Siegel Can you please let me know if you have implemented this property atlassian.allow.insecure.url.parameter.login at your end to make login work again using url.

[Roland Siegel]

Hi @Rahul Jain ,

we actually did not activate this configuration as Atlassian marked this as insecure and switched is off. We will change our software to use the personal access tokens.

[Rahul Jain]

Thanks @Roland Siegel for the update.

[Kishan Sharma]

@Rahul Jain We have Single Sign On enabled for authentication.

[Rahul Jain]

@Roland Siegel @Kishan Sharma 

Actually in our application, we were using one system user to login to confluence. So not sure what is the alternative way to achieve the same now.

We can't create account for each of our application user.

Can you please point out to any documentation on how to acheive the same behaviour now with either single sign or personal access token, so that login screen will not be displayed to end user and we will login him behind the scenes.

Any assistance you can provide would be greatly appreciated

[Kishan Sharma]

If you want to enable SSO, you can refer this Documentation.