You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How can I make the module work with old self-hosted Jira v8.7.1, where custom authorization based on cookies is used?
The documentation (I'm referring to 2.1.2.1. Cookie Based Authentication) mentions only usage of username+password for such authorization. Such approach doesn't work when custom service is invoked for authentication (it shows own page and use other means to verify the identity).
Instead of username+password I'd like to pass the prepared cookies JSESSIONID, atlassian.xsrf.token and others (as explained in JIRA REST API: Cookie-based Authentication + JIRA REST API calls fail when using JSESSIONID cookie authentication using urlfetch), which I get from the custom authentication service.
Any guidelines on that?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
How can I make the module work with old self-hosted Jira v8.7.1, where custom authorization based on cookies is used?
The documentation (I'm referring to 2.1.2.1. Cookie Based Authentication) mentions only usage of username+password for such authorization. Such approach doesn't work when custom service is invoked for authentication (it shows own page and use other means to verify the identity).
Instead of username+password I'd like to pass the prepared cookies
JSESSIONID,atlassian.xsrf.tokenand others (as explained in JIRA REST API: Cookie-based Authentication + JIRA REST API calls fail when using JSESSIONID cookie authentication using urlfetch), which I get from the custom authentication service.Any guidelines on that?
Beta Was this translation helpful? Give feedback.
All reactions