Hi
Thanks very much for the help so far, it worked after I reorganized the
setup some. But now a new error can, maybe you could help, it seems like the
token returned can't be referenced, got this message
Cannot obtain token identifier
So I guess I've to add a identifier to my token somehow, but little unsure
on how to do this. Can it only be an attribute in the token called id, like
this
<RequestedSecurityToken>
<RoleInProject xmlns="http://my.namespace/"; id="1234567">
<Role>ADMIN</Role>
<Project>testu_project</Project>
</RoleInProject>
</RequestedSecurityToken>
Or does the id attribute have to have a special format, type etc
I read in the spec about RequestedAttachedReference and it said:
"Since returned tokens are considered opaque to the requestor, this optional
element is specified to indicate how to reference the returned token when
that token doesn't support references using URI fragments"
So I guess I want to know how to make my token in a way that it could be
referenced.
cheers, Håkon
2009/3/10 Massimiliano Masi <[email protected]>
> Hi,
>
> Quoting Håkon Sagehaug <[email protected]>:
>
>> Can you specify that an interaction should be final or not? I looked at
>> the
>> messages exchanged in rampart sample 05, and there the
>> RequestedSecurityTokenResponse was not wrapped inside a
>> RequestedSecurityTokenResponseCollection
>>
>
> Look at the Rampart's source, STSClient,
> processIssueResponse:
>
> if (version == RahasConstants.VERSION_05_12) {
> //The WS-SX result will be an RSTRC
> rstr = result.getFirstElement();
> }
>
> This means that the STS has to return the RSTRC. If you use a single
> round trip, then the template is always RST/RSTRC.
>
> I already posted it in the rampart-dev ml:
>
> <
> http://www.nabble.com/Misunderstanding-in-rampart-processIssueResponse-td21706796.html
> >
>
> and also look at the OASIS' ml:
>
> <http://lists.oasis-open.org/archives/ws-sx-comment/200901/msg00002.html>
>
> Ciao,
>
> Massimiliano
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
>
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
