It seems that I have found simple solution for Jira. But confluence
solution is similar.
That needed:
1. new jsp page /user-not-exists.jsp with explanations why user haven't
been logged into Jira.
2. new web-server filter: UserExistsCheckFilter
Filter gets CAS username and checks if an account with this username
exists in Jira. If user exists next filter is chained.
If account does not exists user is redirected to /user-not-exists.jsp page
3. web.xml modification:
<filter>
<filter-name>UserExistsCheckFilter</filter-name>
<filter-class>org.uj.cas.jira.UserExistsCheckFilter</filter-class>
</filter>
<filter-mapping>
<filter-name>UserExistsCheckFilter</filter-name>
<url-pattern>/login.jsp</url-pattern>
</filter-mapping>
<filter-mapping>
<filter-name>UserExistsCheckFilter</filter-name>
<url-pattern>/secure/Dashboard.jspa</url-pattern>
</filter-mapping>
--
Michal Pysz
Information Technology Section
Jagiellonian University
Krakow, Poland
https://login.uj.edu.pl/
http://www.jasig.org/cas/deployments/jagiellonian-university-
> Does anybody solved problem with such scenario:
>
> 1. I don't have account at JIRA
> 2. I'm logging into https://cas.my-host.com
> 3. next I'm going to: http://jira.my-host.com
> Now I'm getting redirection loop.
>
> The same scenario hits Confluence.
>
> Is any way to solve such problem.
> I think that displaying a page with message "you are not permitted to
> enter JIRA" will be enough.
>
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
