Problems with Upsource 2.5 and Jira Auth Module Follow
Hi everyone,
I'm running upsource-2.5.4995 and try to get the jira authentification module to work.
Jira Integration for the projects is possible / works, following the manual for enabling coors in jira, but the login with an jira auth module does not work.
When I do a test login which points to a rest call (seen with firebug) to the url http://myservername.domain:8081/hub/api/rest/authmodules/d85ac8a5-0977-41b9-a793-5f7321d32575/resolve I got a 404 error, and Exceptions in the upsource log
The website link is http://servername.domainame:8081/hub/authmodules/d85ac8a5-0977-41b9-a793-5f7321d32575so the uniq ID seem to fit.q
I tested this also with the Active Directory Login Module and here the rest call does work an return code 200.
Any ideas thats going wrong?
Cheers Frank
08:56:32,361 WARN [BaseExceptionMapper ] REST exception for URL: /hub/api/rest/authmodules/d85ac8a5-0977-41b9-a793-5f7321d32575/resolve
[2015-12-16 08:56:32,371] jetbrains.jetpass.rest.common.JetPassRestException: Doesn't exist or is not accessible
[2015-12-16 08:56:32,371] at jetbrains.jetpass.rest.common.ExceptionExt.checkExists(ExceptionExt.java:67)
[2015-12-16 08:56:32,371] at jetbrains.jetpass.rest.api.authority.AuthModuleSubresource.post_Resolve(AuthModuleSubresource.java:84)
[2015-12-16 08:56:32,371] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[2015-12-16 08:56:32,371] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[2015-12-16 08:56:32,372] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[2015-12-16 08:56:32,372] at java.lang.reflect.Method.invoke(Method.java:497)
[2015-12-16 08:56:32,372] at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)
[2015-12-16 08:56:32,372] at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:164)
[2015-12-16 08:56:32,372] at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:181)
[2015-12-16 08:56:32,372] at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$TypeOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:20
3)
[2015-12-16 08:56:32,372] at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:101)
[2015-12-16 08:56:32,372] at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389)
[2015-12-16 08:56:32,372] at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347)
[2015-12-16 08:56:32,373] at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102)
[2015-12-16 08:56:32,373] at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:305)
Please sign in to leave a comment.
Hi Frank,
It's a known issue, please watch it here - https://youtrack.jetbrains.com/issue/JPS-3325
Sorry for that inconvenience.
Hi Artem,
no problem, thanks for your answer. The Issue you linked points out, that this problem does relate to Jira 7, but we are actually using v6.4.1....
Regards Frank