[JBoss JIRA] (ELY-929) AuthenticationConfiguration uniqueness enhancements
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-929?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-929:
---------------------------------
Fix Version/s: 1.1.0.CR6
(was: 1.1.0.CR5)
> AuthenticationConfiguration uniqueness enhancements
> ---------------------------------------------------
>
> Key: ELY-929
> URL: https://issues.jboss.org/browse/ELY-929
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Authentication Client
> Reporter: David Lloyd
> Assignee: David Lloyd
> Fix For: 1.1.0.CR6
>
>
> Apply some enhancements to AuthenticationConfiguration uniqueness.
> * Add admonishing JavaDoc to {{useCallbackHandler}} to point out the importance of per-identity uniqueness of the callback handler
> The following also may be possible and useful:
> * Modify the {{AuthenticationConfiguration}} process to capture instances for {{Supplier}}-driven components at the time the configuration is used via the {{AuthenticationContextConfigurationClient}}
> * Add a variation of {{useCallbackHandler}} which accepts a {{Supplier<CallbackHandler>}}, or a {{Function<T, CallbackHandler}} and a {{T}}, allowing constructor refs to be given
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (ELY-849) Rename setMechanismProperties to setSaslMechanismProperties
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-849?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-849:
---------------------------------
Fix Version/s: 1.1.0.CR6
(was: 1.1.0.CR5)
> Rename setMechanismProperties to setSaslMechanismProperties
> -----------------------------------------------------------
>
> Key: ELY-849
> URL: https://issues.jboss.org/browse/ELY-849
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Authentication Client
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 1.1.0.CR6
>
>
> If we later add HTTP mechanisms we have no way to differentiate between HTTP and SASL mechanism properties.
> We could probably share properties and rely on protocol matching in the MatchRule but as a single AuthenticationConfiguration will support both HTTP and SASL I think independent properties will be required.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (ELY-1312) Further Scoping and Caching Enhancements to the SpnegoAuthenticationMechanism
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-1312?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse resolved ELY-1312.
-----------------------------------
Resolution: Done
> Further Scoping and Caching Enhancements to the SpnegoAuthenticationMechanism
> -----------------------------------------------------------------------------
>
> Key: ELY-1312
> URL: https://issues.jboss.org/browse/ELY-1312
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: HTTP
> Environment: #
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 1.1.0.CR5
>
>
> Currently the SpnegoAuthenticationMechanism caches against the connection scope and uses the cached GssContext to recreate the identity.
> We should consider the following: -
> # Using the same cached identity mechanism as is used by FORM authentication.
> # Adding configuration to specify which scope to cache against.
> # Add an option to disable caching entirely, this would need to take into account cases where continuation is required as that would become unsupported.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3147) Getting org.osgi.framework.AdminPermission check failed with security manager
by Girish Pathak (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3147?page=com.atlassian.jira.plugi... ]
Girish Pathak commented on WFCORE-3147:
---------------------------------------
I tried uploading my sample war it is not allowing me to upload, I am getting exception saying file exceeds maximum size limit set by the administrator(20.00 MB) and even I tried zipping my sample war , attaching but still it is exceeding the limit
> Getting org.osgi.framework.AdminPermission check failed with security manager
> -----------------------------------------------------------------------------
>
> Key: WFCORE-3147
> URL: https://issues.jboss.org/browse/WFCORE-3147
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 3.0.0.Beta30
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Priority: Trivial
>
> Despite permission is granted in standalone.xml
> {code}
> <minimum-set>
> <permission class="org.osgi.framework.AdminPermission" name="(id=0)" actions="context"/>
> </minimum-set>
> {code}
> During deployment there is exception
> {code}
> java.security.AccessControlException: WFSM000001: Permission check failed (permission "("org.osgi.framework.AdminPermission" "(id=0)" "context")" in code source "(vfs:/content/myapp.war/WEB-INF/lib/org.eclipse.equinox.servletbridge_1.2.100.v20120209-2014.jar
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months