Changes in "Configure RelyingParty" are not saved

[sahilIT2020]

Steps to reproduce

1. Click on Add Trust relationship
2. Attach sample metedata file
3. Click on "Configure RelyingParty" and add SAML2SSO and leave other options as default
4. Release attributes
5. Click on Save
6. Search for the TR created in above steps
7. Click on "Configure RelyingParty"

Expected : You should see "SAML2SSO" selected with default values
Actual: Nothing is selected.

Version gluu-server-3.0.0 (2-BETA3~trusty+Ub14.04)

[shekhar16]

Are you getting any exception.

[nynymike]

Can you test if the TR entry in LDAP is updated? This is a critical bug report.

[sahilIT2020]

gluuProfileConfiguration are getting saved in LDAP

<rp:ProfileConfiguration xsi:type="saml:SAML2SSOProfile"
includeAttributeStatement="true"
assertionLifetime="150"
assertionProxyCount="0"
signResponses="conditional"
signAssertions="never"
signRequests="conditional"
encryptAssertions="conditional"
encryptNameIds="never"
/>

Error in logs
2017-01-18 04:55:36,851 ERROR [pool-2-thread-3] [org.gluu.oxtrust.ldap.service.Shibboleth3ConfService] (Shibboleth3ConfService.java:322) - Failed to parse stored metadataFilter configuration for trustRelationship inum=@!495F.F2BE.310E.8C33!0002!C48C.C103!0006!D29C.653A,ou=trustRelationships,inum=@!495F.F2BE.310E.8C33!0002!C48C.C103,ou=appliances,o=gluu
org.xml.sax.SAXParseException: The prefix "rp" for element "rp:ProfileConfiguration" is not bound.

[shekhar16]

@uboznikov please check this exception it is related to the xml file shiboleth3.

[uboznikov]

Fix to #363 causes org.xml.sax.SAXParseException

@yurem We may need to review the fix...

[uboznikov]

Thanks @yurem after latest fix configure RP is now ok.

@sahiliamsso Please re-test in new build. Thanks.

[yurem]

Can you retest it on new beta build?

[sahilIT2020]

Fixed, verified on gluu-server-3.0.0 (2-BETA4~trusty+Ub14.04)