on 04-14-2014 5:23 PM
Hi All,
We have an application in SUP 2.1.3 which now access a SOAP webservice and is now running fine. A new change in the webserice is that, the existing websrvice would become a secured webservice. So, I would like to know what changes we need to make in SUP in order to see that the existing application would not break in future.
Below are the details of current working environment:
SUP 2.1.3 cluster
SOAP webservice
Relay cluster and 1 load balancer
ClientvaluePropagating login module and HTTPauth model are being used.
Please let me know for additional information.
Regards,
Shiv
Hi guys,
Can you help me about the above mentioned issue, let me know if you need more information:
Jitendra Kansal , Marvin Hoffmann, Midhun VP
Thanks,
Shiv
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have found the answer, below is the explanation
The secured webservices expect additional set of credentilals which would be not known to the user. These credentials are configured at the back end. In SUP we can configure these at the connection pool setting ( Domain--> connections-->new Connection)
Attached is the screen shot for the reference.
Thanks,
Shiv
User | Count |
---|---|
84 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.