We recently upgraded to Atlassian Confluence 7.13.0 (Data Centre) and after that login via url is not working.
I found this article which says we can use a workaround method i.e. to use atlassian.allow.insecure.url.parameter.login as true
https://confluence.atlassian.com/doc/confluence-7-10-upgrade-notes-1026054305.html
Is this system property applicable for 7.13.0 as well?
As the document states, you can use the workaround. I would suggest you migrate to the more secure option, such as personal access tokens.
Thanks for the reply @Brant Schroeder
The artical mentioned is for 7.10 but I am using 7.13, so will workaround work for that as well.
Actually we can't give anonymous access and also we can't create confluence user for every application user so we were using one system user for authentication purpose.
In short authentication was happening behind the scenes using login via url with system user credentials. We can't show confluence login screen to application user as they don't have their users on confluence.
So will personal access token option workout in that manner and will we get static token for use?
Or is there any other alternative to implement the same behaviour.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.