nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

How to disable WS-Security header??

nathant99

Hi all,

I'm using the Alfresco web services API but the WS Client (Tibco BusinessWorks) is not allowing me to set the ticket value dynamically. I've tried so many ways to fix it on the Tibco side but there's no solution that I found.

Is there a way to disable the WS Security check and just use the ticket as a simple parameter in the SOAP header like in the old Alfresco versions??

Thanks,
–Nathan

Find more posts tagged with

Comments

rwetherall

Hi,

The Alfresco web services have always used the WS Security header to pass the ticket information to the server.

The ticket is plucked out of the password parameter and cross checked within the server to ensure the request can proceed.

So long as you construct the WS Security header correctly authentication at the repository should occure without problem,

Cheers,
Roy

nathant99

Roy,

Thanks for your reply..

I got it working by using a workaround.

I have Tibco BW send the ticket in the SOAP header without the WS security header by modifying Alfresco WSDLs. Then on the server side, I created an Axis handler that adds the WS security header to the SOAP header before the WS security handler is invoked.

BTW, I had to fix the handler code in WSS4J 1.5.1 b/c it couldn't deal newline characters after the <SOAP:Header> tag

Regards,
–Nathan

Hi,

The Alfresco web services have always used the WS Security header to pass the ticket information to the server.

The ticket is plucked out of the password parameter and cross checked within the server to ensure the request can proceed.

So long as you construct the WS Security header correctly authentication at the repository should occure without problem,

Cheers,
Roy