Shibboleth Developers

If you are using the JNDIDirectoryDataConnector, you may verify if the binary attribute prints as something like [b@03893279?

 

The best way is to use the resolver batch scripts in the bin directory for quick testing, rather than use the SHAR. Binary attributes may be returned as byte[] from JNDIDirectoryDataConnector. However the default ValueHandler used by SimpleAttributeDefinition is a "StringValueHandler", it does a "toString()" on the attribute value returned from JNDI.

 

If you indeed see the value printed as something like [b@65464613 it is because the toString() on byte arrays returns that. You should create a Base64ValueHandler that would take the byte[] and convert it to a Base64 string, which can then be easily handled in all assertions.

 

-- Vishal

 

 

 

---

From: Zhi Qing Wu [mailto:]
Sent: Friday, October 01, 2004 8:01 PM
To:
Subject: A Binary Attribute

 

Hello,

 

We have a question about attributes sent from AA to Shar.

 

We inserted a binary record (a certificate) into a LDAP server. AA read the record and tried sending it with other text records to Shar via SAML protocol. (We have defined two new attributes in relevant LDAP schemes, one for the binary record and the other for a text record. We have revised relevant configuration files such as ARP.xml, resolver.ldap.xml and AAP.xml to make sure two records will not be stopped due to these configuration files.)

 

After several experiments, by reading shar.log, we found the text record (we defined) has been properly transmitted from the AA to the Shar but we can not find the binary record in shar.log. 

 

Question: is transmitting binary record (such as an attribute certificate) supported by SAML in shibboleth? If yes, how to change the configuration to send the binary record from AA to Shar?

 

Any advice would be appreciated.

 

Zhi Qing

---

ALL-NEW Yahoo! Messenger - all new features - even more fun!