Forum Discussion
bobkaine
2 years agoNew Contributor
I'm receiving the exact same error after upgrading from 3.10.1 to 3.46.1.
Did you ever figure out what was causing this behavior, how to fix it?
- thatsthat2 years agoContributor
Hi bobkaine - no solution yet; I raised a ticket with support on May 19th .. they just got back to me June 6th and I have followed up with them again earlier this week and they said they are still investigating. As soon as I hear of a solution I will post here. Has to be some global setting that has changed. The APIs use WS-Security ( https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wss ) so wonderingif it is specific to this?
Related Content
- 2 years ago
- 6 years ago
- 4 years ago