Answers to: Calling NTLM protected REST service with SSO

Comment by Reguel Wermelinger on Reguel Wermelinger's answer

Reguel Wermelinger — Mon, 15 Oct 2018 05:45:01 -0400

I've just found an older issue that already discusses this need: https://jira.axonivy.com/jira/browse/XIVY-1063 I added you to the watchers. Feel free to negotiate its priority with our PO. Maybe you can enrich the issues with infos about your current customer project that would benefit from it.

Comment by peters on Reguel Wermelinger's answer

peters — Mon, 15 Oct 2018 04:29:40 -0400

I think both scenarios could be valid, but if necessary to decide, I would probably prefer the Engine (thinking about background jobs and the like).

Answer by Reguel Wermelinger

Reguel Wermelinger — Mon, 15 Oct 2018 03:02:02 -0400

I've just inspected the NTLMAuthenticationFeature of our REST clients. It looks like currently we explicitly block the re-usage of the user/password which are known by to the JVM. We enforce the usage of the username+password defined in our own webservice client configuration. So no, today SSO will not work with REST client calls.

For a future improval. What would you expect from an NTLM/SSO feature? Should it re-use the credentials from the current user that works with ivy or should it be the account that runs the JVM (axonIvyEngine)?