[JBoss JIRA] (WFLY-8418) Enhance the way licenses are presented and fix inconsistencies
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-8418?page=com.atlassian.jira.plugin.... ]
James Perkins reopened WFLY-8418:
---------------------------------
> Enhance the way licenses are presented and fix inconsistencies
> --------------------------------------------------------------
>
> Key: WFLY-8418
> URL: https://issues.jboss.org/browse/WFLY-8418
> Project: WildFly
> Issue Type: Enhancement
> Components: Build System
> Reporter: Petr Sakař
> Assignee: Petr Sakař
> Priority: Critical
> Labels: downstream_dependency
> Fix For: 11.0.0.Alpha1
>
>
> We need to provide a better view of the existing license information presented in the docs/licenses.xml file, in the form of a docs/licenses.html file that lists:
> Group/Artifact/Version/License (name+original URL)/Local Copy(relative pathname link to local copy of the license in the licenses dir).
> This can be achieved with an .xslt transformation that runs as part of the build process, which produces the desired licenses.html, and it would allow us to zip and forward the entire doc/licenses directory to a client that wants to evaluate the licenses used in Wildfly.
> In addition we need to sanitize a bit the presented licensing information:
> Licenses.html *MUST* contain a reference to the Wildfly version it applies to. It *MUST* also contain a timestamp (or build number) to uniquely identify it should it need changes within one Wildfly release cycle.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ELY-1029) Support clients that provide an optional CallbackHandler
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-1029?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated ELY-1029:
----------------------------------
Fix Version/s: 1.1.0.Beta51
(was: 1.1.0.Beta50)
> Support clients that provide an optional CallbackHandler
> --------------------------------------------------------
>
> Key: ELY-1029
> URL: https://issues.jboss.org/browse/ELY-1029
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Authentication Client
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 1.1.0.Beta51
>
>
> Clients such as the WildFly CLI provide a CallbackHandler implementation in case it is needed and not as a sign that it must be used, i.e. the desired outcome is that if the information required can be obtained from the configuration then authentication proceeds without interaction with the end user.
> Neither the CLI or the end user should be required to be fully aware of the underlying security configuration.
> This is similar to web browser HTTP authentication where there is only an interaction with the user if actually required.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ELY-715) SPNEGO: missing negstat field in the first reply
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-715?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-715:
---------------------------------
Fix Version/s: 1.1.0.Beta51
(was: 1.1.0.Beta50)
> SPNEGO: missing negstat field in the first reply
> ------------------------------------------------
>
> Key: ELY-715
> URL: https://issues.jboss.org/browse/ELY-715
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Authentication Mechanisms
> Reporter: Jan Kalina
> Assignee: Darran Lofthouse
> Fix For: 1.1.0.Beta51
>
>
> When the client sends an initial SPNEGO token with Kerberos as preferred mechanism and includes an invalid kerberos token, then client expects to see the {{WWW-Authenticate}} HTTP header with SPNEGO response {{negTokenResp[ negState = reject ]}}.
> As stated in [SPNEGO specification|https://tools.ietf.org/html/rfc4178#section-4.2.2] negstat is required in first reply:
> {code:borderStyle=dashed}
> negState
> ...
> This field is REQUIRED in the first reply from the target, and is
> OPTIONAL thereafter. When negState is absent, the actual state
> should be inferred from the state of the negotiated mechanism
> context.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month