Identity Asserter / Token always decoded / WLS 7.0

Question

Hello,
i am implementing a perimeter authentication. A user/password is passed as a cookie.
Cookies are identified with SP1 now as token and passed to the identity asserter.
The problem is only, that the tokens are always base64 decoded by the web-container
out of my control, even if the cookie itsself is not base64 encoded.
Thanks.
Frank

Answer 1

Hi Frank
I just made some tests with WLS 7.0 SP1, an identity asserter and
HTTP-Unit-test as client.
With encoding the cookie it works. Without encoding it doesn't work.
Your're right the WLS security framework always base64-decodes the cookie
value.
The WLS framework presumes that the cookie value is encoded.
This is also written in the comment of the sample in
SamplePerimeterAtnClient.java:
// base 64 encode it. The webapp container (that is, internal WLS code)
will
// base 64 decode the token. The decoded string will be passed to the..
You MUST send a base64-encoded cookie value to a WLS 7.0!. or wait for a
patch.
Alain
"Frank Arendt" <Frank,.[email protected]> wrote in message
news:3dbee0b3$[email protected]..
>
Hello,
i am implementing a perimeter authentication. A user/password is passed asa cookie.
Cookies are identified with SP1 now as token and passed to the identityasserter.
The problem is only, that the tokens are always base64 decoded by theweb-container
out of my control, even if the cookie itsself is not base64 encoded.
Thanks.
Frank