You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi All,
Recently, i got to work wiht Shibboleth idp, i was trying out with basic metadata configuration.
however, at the shibboleth idp, they had some relay/nameid configurations to encrypt always.
so, if authnrequest has been made, it was rejecting saying encryption parameters are not right.
but, encryption data was there, finally, adding the encryptionmethod along with the certificate worked.
it makes sense, because, they want to know what is the encryptionmethod(algorithm) supported. having this along with "use"=encryption options, have worked.
so, i wanted to inform that, it is very simple change, can I check-in the code. the code list all the encryption lsited in constatnts.py and updates to the meatadata in metadata.py.
if i update, what is the criteria. and mechanism. lke creating a branch, review and merget?
thanks,
Kalpa.
The text was updated successfully, but these errors were encountered:
is not very common the need of encrypting in the SP side, at the end, no confidential data is sent on AuthNRequest, LogoutRequest and LogoutResponses, with the exception of the NameId, but you could use persistent NameID to anonymize the user.
That said, if I'm not wrong you want to expose the md:EncryptionMethod in addition to the ds:KeyInfo when md:KeyDescriptor has use="encryption".
For that I believe we need to extend the Metadata builder to support an additional parameter encryption_method=None
and then extend as well the methods _add_x509_key_descriptors and add_x509_key_descriptors and inside it, have something like:
Hi All,
Recently, i got to work wiht Shibboleth idp, i was trying out with basic metadata configuration.
however, at the shibboleth idp, they had some relay/nameid configurations to encrypt always.
so, if authnrequest has been made, it was rejecting saying encryption parameters are not right.
but, encryption data was there, finally, adding the encryptionmethod along with the certificate worked.
it makes sense, because, they want to know what is the encryptionmethod(algorithm) supported. having this along with "use"=encryption options, have worked.
so, i wanted to inform that, it is very simple change, can I check-in the code. the code list all the encryption lsited in constatnts.py and updates to the meatadata in metadata.py.
if i update, what is the criteria. and mechanism. lke creating a branch, review and merget?
thanks,
Kalpa.
The text was updated successfully, but these errors were encountered: