[
http://java.net/jira/browse/JASPIC_SPEC-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358071#action_358071 ]
arjan tijms commented on JASPIC_SPEC-1:
---------------------------------------
Even though the method does not seem to appear in the PDR javadoc, I found one reference to it here: GLASSFISH-19814, so it does seem to be a Servlet 3.1 method ;)
> AppContextID of Servlet profile includes name of virtual host; for which Servlet provides no portable api
> ---------------------------------------------------------------------------------------------------------
>
> Key: JASPIC_SPEC-1
> URL: http://java.net/jira/browse/JASPIC_SPEC-1
> Project: jaspic-spec
> Issue Type: Bug
> Reporter: monzillo
> Assignee: monzillo
>
> During programmatic AuthConfigProvider registration - especially
> self-registration via
> AuthConfigFactory.registerConfigProvider(AuthConfigProvider provider,
> String layer,
> String appContextID,
> String description);
> the AuthConfigProvider has no portable way to determine the name of the virtual
> host, and thus to register using the same virtual host name that will be used
> by the runtime in its call to
> AuthConfigFactory.getConfigProvider(String layer, String appContextID,
> RegistrationListener listener);
> Servlet 3.1 does not intend to provide a portable api by which the name of the
> virtual host can be obtained.
> this problem was first reported by Arjan Tijms
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://java.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira