[Openam] OpenAM + DAUI : X509 authentication issue

Sébastien Stormacq sebastien.stormacq at gmail.com
Wed Nov 24 16:41:46 GMT 2010


Hello Allan,

Because CU is not deploying OpenAM (yet) but stock OpenSSO.
And we do not feel comfortable to combine DAUI from OpenAM with OpenSSO

Seb


On 24 Nov 2010, at 13:52, Allan Foster wrote:

> of course,  the fix in OpenAM DAS to support the retreival of the HTTPRequest should make this pointless?
> 
> Why not just set the property as referenced by Steve?
> 
> Allan
> 
> On 11/24/10 19:49, Victor Ake wrote:
>> 
>> Seb,
>> We have not tested the modification suggested. It is more than a patch.
>> If you guys are in a hurry, what you can do in the mean time  is take
>> those modifications, implement the module as a Custom module and test it.
>> 
>> Regards,
>> 
>>   Victor
>> 
>> 
>> 
>> Sébastien Stormacq wrote:
>>> Hello,
>>> 
>>> We are currently deploying OpenAM for a customer @ Luxembourg.
>>> CU is willing to use X509 authentication + DAUI
>>> 
>>> However, we are hitting this bug
>>> : https://bugster.forgerock.org/jira/browse/OPENAM-18
>>> 
>>> As the source code of a patch is given in the bug description, I
>>> wonder if / when this will be included in the trunk.
>>> 
>>> Any help ?
>>> 
>>> Thanks
>>> 
>>> Seb
>>> 
>>> Begin forwarded message:
>>> 
>>>> *From: *frederic Van De Velde <frederic.vandevelde at paradigmo.com
>>>> <mailto:frederic.vandevelde at paradigmo.com>>
>>>> *Date: *24 Nov 2010 10:05:12 GMT+01:00
>>>> *To: *Sébastien Stormacq <sebastien.stormacq at oracle.com
>>>> <mailto:sebastien.stormacq at oracle.com>>
>>>> *Subject: **opensso problem chez Luxtrust*
>>>> 
>>>> Salut Seb,
>>>> 
>>>> Je suis en train de configurer un environement opensso/daui chez
>>>> Luxtrust pour faire de l'authentification par certificat.
>>>> L'authentification fonctionne parfaitement lorsqu'on va en direct sur
>>>> le serveur opensso mais lorsqu'on passe par le daui le serveur
>>>> opensso ne trouve pas le certificat utilisateur.
>>>> 
>>>> J'ai trouvé un bug chez Forgerock
>>>> (https://bugster.forgerock.org/jira/browse/OPENAM-18) qui correspond
>>>> exactement au problème et il y a même quelqu'un qui a publié un code
>>>> qui pourrait fixer le problème
>>>> par contre je ne trouve aucune commit de ce code chez Forgerock,
>>>> l'idée était de prendre le module Cert.class corrigé par Forgerock et
>>>> de l'utiliser.
>>>> 
>>>> Tu pourrais me donner un coup de main sur ce coup là ?
>>>> 
>>>> Merci,
>>>> Fred.
>>>> 
>>> --Seb
>>> 
>>> 
>>> 
>>> 
>>> 
>>> ------------------------------------------------------------------------
>>> 
>>> _______________________________________________
>>> Openam mailing list
>>> Openam at forgerock.org
>>> https://lists.forgerock.org/mailman/listinfo/openam
>>>   
>> _______________________________________________
>> Openam mailing list
>> Openam at forgerock.org
>> https://lists.forgerock.org/mailman/listinfo/openam
> 
> 
> -- 
> <ForgeRock-226x60.png>	 Allan Foster VP Technical Enablement
> e: allan.foster at forgerock.com
> t: +1.503.334.2546
> w: www.forgerock.com
> The New home for OpenSSO -- OpenAM! It's gonna be BIG!
> _______________________________________________
> Openam mailing list
> Openam at forgerock.org
> https://lists.forgerock.org/mailman/listinfo/openam

--Seb




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.forgerock.org/pipermail/openam/attachments/20101124/61fab07d/attachment.html>


More information about the OpenAM mailing list