uid attribute encoding

[Matthew Slowe]

On 2022-02-24 16:08, Bryan K. Walton via users wrote:
> I'm trying to configure our IdP for integration with a vendor.  We need
> to pass uid as the remote user attribute.  In my testing, I'm passing
> the attribute "bwalton".  However, the vendor is saying that the
> attribute value is coming across like:
> 
> AAdzZWNyZXQxy1bOAaCA9D1blv...
> 
> I think this is the base64 encoded version of bwalton.  If so, is there
> a way to *not* encode the uid attribute value?

"AAdzZWNyZXQxy1bOAaCA9D1blv" decodes to:

00000000: 0007 7365 6372 6574 31cb 56ce 01a0 80f4  ..secret1.V.....
00000010: 3d5b                                     =[

Which doesn't look much like your uid :-)

It's worth checking the idp-process.log to see what's going out (you may 
need to crank up the logging to DEBUG to see it) - it may be sufficient 
to use "aacli" with the "--saml2" flag to generate an unencrypted 
assertion... I doubt Shibboleth is generating this.

That looks like a bit of cookie to me.

-- 
Matthew Slowe (GPG: 0x6BE0CF7D04600314)
Senior Technical Consultant and Support specialist, Jisc
Team: 0300 300 2212, option 2
Lumen House, Library Avenue, Harwell Oxford, Didcot, OX11 0SG