[jboss-jira] [JBoss JIRA] (ELY-514) Define standard properties for use by HTTP authentication mechanisms.

[Darran Lofthouse (JIRA)]

    [ https://issues.jboss.org/browse/ELY-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198364#comment-13198364 ] 

Darran Lofthouse commented on ELY-514:
--------------------------------------

Having the realm name in there from the web.xml will also allow this to be checked against the configured realm names for the mechanism without having to default to using the first if another is matched.

> Define standard properties for use by HTTP authentication mechanisms.
> ---------------------------------------------------------------------
>
>                 Key: ELY-514
>                 URL: https://issues.jboss.org/browse/ELY-514
>             Project: WildFly Elytron
>          Issue Type: Enhancement
>          Components: API / SPI, HTTP
>            Reporter: Darran Lofthouse
>            Assignee: Darran Lofthouse
>             Fix For: 1.1.0.Beta6
>
>
> There is a small set of configuration properties that make sense to be passed to the mechanism factory as the mechanism is created, using properties also allows us to define these properties in the subsystem configuration as well.
> Main properties being: -
>   Context Path
>   Realm
>   Login Page
>   Error Page
> These items are already mapped in the pure Undertow implementation but make sense both in servlet and non servlet cases.  Incidentally Undertow supports custom properties per mechanism which we will also be able to pass in using the same mechanism.
> I did also consider if we should use the existing scopes for this but you still end up with a naming convention and in that case you also risk your naming conflicting with something else stored in that scope.
> A final option could be a configuration scope but that would be effectively duplicating the properties Map we already have which aligns with the same approach taken by SASL mechanisms.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)