Use Case:
For jira server we're using crowd SSO for authentication. Now we want to establish a link between jira and a cloud application, for which we'll assign jira with a public IP and we'll create a new <Connector port="number"> to serve it. For internal reasons the public IP can't be dns'ed, so crowd (SSO) won't authenticate requests with that IP. We have tested the raw IP setup to work when using JiraSeraphAuthenticator in seraph-config.xml (so no SSO, as when provided by SSOSeraphAuthenticator), but we don't want this, since then we would lose SSO for regular users.
Question 1:
Could jira be configured with two <Connector port="number">, so it bypasses crowd SSO or crowd altogether for one of them, while authenticating with crowd SSO with the other one.
Question 2:
Is there any other alternative for my use case
