Announcement Announcement Module
No announcement yet.
keystore-metadata bug? Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • keystore-metadata bug?

    hi all, please help!

    I 'm using Spring Security - SAML Extension.
    i've created my keystore ( Configure keyStore bean ecc ... application is loading credential on start up)

    i'm using default metadata ( Metadata of the hosted SP will be generated automatically after
    deployment )

    i see that aplication ( saml2-core ) create a keyinfo starting from my credential,

    but credential object has real public key of my certificate ( keygen generated , i printed public key from credential object to verify just before keyinfo generation )
    keyinfo object instead has always a default <ds:X509Certificate>MIIDRTCCAi2gAwIBAgIEQUjH.....= =</ds:X509Certificate>

    keyinfo object is used to create metadata page of my sp application.

    so SP metadata generated automatically always has the same declaration of ds:X509Certificate.

    My question: sp metadata ds:X509Certificate should be the public key of the certificate i created with keygen ?
    why generated metadata do not change with different keystore / certificate?

  • #2
    i figured out
    <ds:X509Certificate> in metadata is not public key of my certificate but all of it.
    so metadata is ok.

    idp give me samlp:Response , so sp and idp talk each other.

    but ... i have still an error in the ind

    org.apache.jasper.JasperException: An exception occurred processing JSP page /index.jsp at line 72

    69: <td>
    70: <c:forEach var="attributeValue"
    71: items="${attribute.attributeValues}">
    72: <c:out value="${attributeValue.value}"/>&nbsp;
    73: </c:forEach>
    74: </td>
    75: </tr>

    javax.el.PropertyNotFoundException: Property 'value' not found on type org.opensaml.xml.schema.impl.XSAnyImpl

    any idea ?


    you know what ... i have done this .. and now it works

    <c:catch var ="catchException">
    <c:out value="${attributeValue.value}"/>&nbsp;

    attributeValue.value aren't all of the same class type ...
    Last edited by aleale; Sep 24th, 2012, 11:06 AM.


    • #3
      Thanks for noticing this, trunk now contains a fix.