Skip to content
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

Soap Security Header #37

Closed
victorgp89 opened this issue Feb 18, 2019 · 15 comments
Closed

Soap Security Header #37

victorgp89 opened this issue Feb 18, 2019 · 15 comments

Comments

@victorgp89
Copy link

image

These namespaces must be indicated in the config.yml? Thanks a lot.

@goetas
Copy link
Member

goetas commented Feb 18, 2019

generally yes. I suggest you to have a look at #9

@goetas goetas closed this as completed Feb 18, 2019
@victorgp89
Copy link
Author

Because I've this wsdl : https://cmtpi.siteminder.com/siteconnect/services/siteconnect_v1.1.0.wsdl

And process to generate PHP classes and metadatas give me this error:

image

My yml is like this:

image

@victorgp89
Copy link
Author

In this case I can't solve where the problem is.

@victorgp89
Copy link
Author

Or should I take all the commit changes that you mentioned above?

@goetas
Copy link
Member

goetas commented Feb 18, 2019

as you can see #9 is not complete, you can try to continue on it

@victorgp89
Copy link
Author

But adding the namespace in the yml could not deserialize the headers?

@goetas
Copy link
Member

goetas commented Feb 18, 2019

not really. WSI headers are too complex

@victorgp89
Copy link
Author

Sorry for the inconvenience, because I don't know very well what generates the problem.

If I create the metadatas, headerHandlers and PHP classes from the SoapSecuritym. What do you think would be the next step when processing the header of the wsdl that you have given me?

The library xsd2php accept the attributes:
any_element: true
any_attribute: true

I think this is in YamlDriver but I can see.

Sorry for this. Is for try to solve the problem because for my project I need to be able to process those headers.

Thanks for advance,
Victor

@victorgp89
Copy link
Author

image

I try this yml after create the security xsd but the problem persist:

image

@victorgp89
Copy link
Author

Any update about this? Sorry for disturb

@victorgp89
Copy link
Author

And another simple question:

The attributes in yml: any_element and any_attribute are available in xsd2php project?

Because I have the following error:

Call to undefined method WssWsSecurity\Secext\Security::addToAnyElement()

@goetas
Copy link
Member

goetas commented Feb 19, 2019

I suggest you to have a look at as #9
there you have see how to deal with any-type

@victorgp89
Copy link
Author

It's possible to skips this headers in the process to convert wsdl in php classes and SoapContainer?

Because always return the same:

Can't find the Attribute named {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}#Id.

@victorgp89
Copy link
Author

Because I need to generate the metadata and PHP classes from this wsdl:

https://cmtpi.siteminder.com/siteconnect/services/siteconnect_v1.1.0.wsdl

@victorgp89
Copy link
Author

The last thing, it would be possible to generate a subscriber to extract the header, process it manually and let go with the process.

image

But this is not generic.

Thanks for advance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants