[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [higgins-dev] Problems testing Cloud Selector
|
Hi again, seems that the problem was that I had configured a wrong cardsync endpoint (we have 3 deployed instances) that had not the username I was trying to authenticate.
Seems that the LoginException masks the internal higgins exception that was giving information about the non existence of the user profile in the target cardsync repository. I don't know if this is something that you could control or if it is intended.
Anyway, I have the following files in my STS configuration (from the fusion of cardsync config and STS) and I don't know the real purpose of many and not even when they are used. Could someone help me with this?
hbx.properties Definition of message files that are used on user creation from Azigo
ManagedConfiguration.xml Basic configuration for Higgins STS
ManagedClientConfiguration.xml Unknown
ClientConfiguration.xml Unknown
ClientConfiguration.xml.axis Unknown
ClientConfiguration.xml.wsit Unknown
XMLFileProfileServiceConfiguration.xml Unknown
LocalManagedConfiguration.xml Unknown
PersonalConfiguration.xml Used by CardSync, I guess that has just the self-issued configurations
EclipseManagedConfiguration.xml ¿Test environment?
The following files I believe that are just samples from many testing use cases or environments.
higgins.config.xml
ibm.config.xml
nossl.higgins.config.xml
sun.config.xml
The following I guess that are just configuration schemas used during configuration process.
Configuration.xsd
metadata-wsdl.xml
metadata-schema.xml
metadata-issue-selfsignedsaml-supported.xml
metadata-issue-x509-supported.xml
metadata-issue-username-supported.xml
---
David Campos
Safelayer Secure Communications Developer
DMAG UPC R+D Researcher
Barcelona, Barcelona (Spain)
On Wed, Sep 15, 2010 at 16:39, David Campos
<noymn.the.archangel@xxxxxxxxx> wrote:
Hello all,
I have managed to deploy cloudselector and cloudselector-test (a.k.a. higgins.proxy and higgins.proxy.test) being successful to link both applications with a third internal cardsync component. My problem comes when I try to retrieve user claims from cardsync with Cloud Selector.
Every time I try to authenticate (no matter if the password was correct or not) I get the following error:
The password I use is correct, since I can authenticate in cardsync with Azigo but I don't know how to solve this. I have read that this may be a problem of JAAS, but I have no idea where is JAAS used if it is.
Could you help me?
Thanks,
---
David Campos
Safelayer Secure Communications Developer
DMAG UPC R+D Researcher
Barcelona, Barcelona (Spain)