On Fri, Jun 20, 2008 at 5:56 PM, Parker Grimes <[EMAIL PROTECTED]> wrote:

> Close enough, that got me in the right place. There are actually two
> init-params that need to be changed:
>
>         <init-param>
>             <param-name>login.url</param-name>
>             <param-value>
> https://localhost:8443/cas/login?service=${originalurl}<https://localhost:8443/cas/login?service=$%7Boriginalurl%7D>
> </param-value>
>         </init-param>
>         <init-param>
>             <param-name>link.login.url</param-name>
>             <param-value>
> https://localhost:8443/cas/login?service=http://yourwikiurl.edu/
> </param-value>
>         </init-param>
>
> After changing both of those, it worked! Thanks for the help Scott. I
> updated the wiki page as well http://www.ja-sig.org/wiki/x/gwHP
>
> For anyone else interested in a comparison between the JA-SIG CAS Java
> Client and the Soulwing CAS client read on...
>
> The way the Soulwing CAS client sets up the servlet filters, it essentially
> sends you through CAS to authenticate even for anonymous access to
> Confluence, so if you don't allow anonymous access, it works really well.
> The JA-SIG CAS Java Client allows for anonymous access and sends you to CAS
> when you click the "Log In" link or attempt to access a page that does not
> allow anonymous access.


Our goal, as you noticed :-), is to delegate as much as possible to the
original Confluence authentication mechanisms so that it can manage
anonymous access, etc.  If you experience any problems with it, let us know.

Thanks!
-Scott


>
>
> Parker
>
>
> On Fri, Jun 20, 2008 at 10:15 AM, Scott Battaglia <
> [EMAIL PROTECTED]> wrote:
>
>> I can't recall off the top of my head, but in the seraph-config.xml you
>> may need to change this:
>>
>>         <init-param>
>>             <param-name>login.url</param-name>
>>
>> <param-value>/login.action?os_destination=${originalurl}</param-value>
>>         </init-param>
>>
>> to something like
>>
>>         <init-param>
>>             <param-name>login.url</param-name>
>>             <param-value>https://localhost:
>> /8443/cas/login?service==${originalurl}</param-value>
>>         </init-param>
>>
>> -Scott
>>
>> -Scott Battaglia
>> PGP Public Key Id: 0x383733AA
>> LinkedIn: http://www.linkedin.com/in/scottbattaglia
>>
>> On Fri, Jun 20, 2008 at 10:15 AM, Parker Grimes <[EMAIL PROTECTED]> wrote:
>>
>>> We have a stock Confluence 2.7.1 install. I would be happy to test things
>>> out and contribute to the documentation if I knew what you were talking
>>> about regarding the url:)
>>>
>>> Parker
>>>
>>>
>>> On Thu, Jun 19, 2008 at 2:03 PM, Scott Battaglia <
>>> [EMAIL PROTECTED]> wrote:
>>>
>>>> Parker,
>>>>
>>>> It just came out so I doubt anyone is using it ;-)  That said, I had
>>>> downloaded the stock Confluence demo and managed to CASify that.  I'm not
>>>> sure how much that differs from your own instance.
>>>>
>>>> It looks like however, that the actual url to redirect to needs to be
>>>> configured.   Did I forget that step in the documentation?  It looks like I
>>>> did.  I can't remember off the top of my head where Confluence stores that
>>>> url.
>>>>
>>>> -Scott
>>>>
>>>> -Scott Battaglia
>>>> PGP Public Key Id: 0x383733AA
>>>> LinkedIn: http://www.linkedin.com/in/scottbattaglia
>>>>
>>>> On Thu, Jun 19, 2008 at 12:38 PM, Parker Grimes <[EMAIL PROTECTED]>
>>>> wrote:
>>>>
>>>>>  Hello,
>>>>>
>>>>> I am trying to setup CAS authentication for our Confluence instance
>>>>> using the CAS Java Client 3.1.3 following these instructions
>>>>> http://www.ja-sig.org/wiki/x/gwHP. Has anyone else been able to get
>>>>> this to work following those instructions? Are the instructions complete?
>>>>>
>>>>> This is what I have done so far:
>>>>>
>>>>>    1. Added the cas-client-core-3.1.3.jar and
>>>>>    cas-client-integration-atlassian-3.1.3.jar to my confluence/WEB-INF/lib
>>>>>    directory
>>>>>    2. Added the CasValidationFilter <filter> configuration to
>>>>>    confluence/WEB-INF/web.xml
>>>>>    3. Added the <filter-mapping> to the CasValidationFilter
>>>>>    immediately before the mapping for "login"
>>>>>    4. Changed the authenticator class in
>>>>>    confluence/WEB-INF/classes/seraph-config.xml to
>>>>>    org.jasig.cas.client.integration.atlassian.ConfluenceCasAuthenticator
>>>>>
>>>>> After all those changes, I start up Confluence and attempt to access a
>>>>> page in our wiki that requires authentication and I get sent to the 
>>>>> default
>>>>> Confluence login page rather than being sent through CAS.
>>>>>
>>>>> I have been using the Soulwing CAS Client for 
>>>>> Confluence<http://www.soulwing.org/confluence-cas.jsp>successfully for 
>>>>> some time now, but I thought I would give the new CAS Java
>>>>> Client a try. Any tips would be appreciated, also I am curious to know if
>>>>> anybody is actually using the CAS Java Client with Confluence.
>>>>>
>>>>> Thanks,
>>>>> Parker
>>>>>
>>>>> _______________________________________________
>>>>> Yale CAS mailing list
>>>>> [email protected]
>>>>> http://tp.its.yale.edu/mailman/listinfo/cas
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Yale CAS mailing list
>>>> [email protected]
>>>> http://tp.its.yale.edu/mailman/listinfo/cas
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Yale CAS mailing list
>>> [email protected]
>>> http://tp.its.yale.edu/mailman/listinfo/cas
>>>
>>>
>>
>> _______________________________________________
>> Yale CAS mailing list
>> [email protected]
>> http://tp.its.yale.edu/mailman/listinfo/cas
>>
>>
>
> _______________________________________________
> Yale CAS mailing list
> [email protected]
> http://tp.its.yale.edu/mailman/listinfo/cas
>
>
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas

Reply via email to