-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Derived Key support #9
Comments
@griga3k Can you try the code from the derived_key branch. For your function can you add the following directly after the call to $objWSSE->finalChangesDKT(); file_put_contents("derivkey.xml", $objWSSE->saveXML()); tar that up and send it to me. I need to see what your document looks like before transmission to work on the URI issue. If you happen to have the raw XML which you can get doing similar but at the beginning of the function, that would also be helpful |
@robrichards I did as requested. Thank you! |
Maybe You need more information? |
@griga3k hoping to get some time this week to look more into it |
@robrichards Can I help you somehow to speed up the process? |
@griga3k I just need to find some time. 3 more weeks until I free up a little |
@robrichards Hey! How it is going? :) Any progress on this or news? Thanks! |
@robrichards Hello! Sorry to bother you again, but do you know if my problem can be solved? Maybe you can give me some hints how to accomplish this with your library. |
@robrichards Hi! Is there any chance that we will achieve results? Thanks! |
@robrichards Hi! Is there any plans to implement the DerivedKeyTokens support? Thanks! |
I need to find a working system that uses derived keys it to be able to move forward on this |
Hello!
I know that you maintain this wonderful xmlseclib library which I am currently using.
And I have a question about it, maybe you could help me with finding a proper soultion.
Here is a problem:
This is the WS-POLICY for the service:
The problem is following:
According to POLICY (RequireDerivedKeys), user needs 2 DerivedKeyTokens (one for signing, other for encrypting).
And soap-wsse.php, unfortunatelly, lacks this functionality.
Therefore I added my own functions to cover that.
To create keys, I use following p-sha1 function: http://stackoverflow.com/questions/19590675/implementation-of-p-sha1-algorithm-in-php
According to POLICY (EndorsingSupportingTokens), we need to sign already created signature.
This implementation is also missing in soap-wssse.php.
I created my own function for that, but I'm not sure if it works correctly.
As a result, I receive following response after I send generated XML:
CryptographicException: Unable to resolve the '#...' URI in the signature to compute the digest.
Can you please help me with those tokens? Do you find it reasonable to add such support for DerivedKeyToken into your class?
Thank you!
The text was updated successfully, but these errors were encountered: