[JBoss JIRA] (ELY-376) Password policies
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-376?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-376:
---------------------------------
Fix Version/s: 1.1.0.Beta6
(was: 1.1.0.Beta5)
> Password policies
> -----------------
>
> Key: ELY-376
> URL: https://issues.jboss.org/browse/ELY-376
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: API / SPI, Passwords, Realms
> Reporter: Darran Lofthouse
> Assignee: David Lloyd
> Fix For: 1.1.0.Beta6
>
>
> Probably needs a design discussion first but we need to review where password policies fit in to the overall solution.
> We may say that policy handling is really the responsibility of the actual realm implementation, after all items such as history are going to be very realm specific.
> However there may also be a case in the generic sense that where a modifiable realm is in use a policy is desired to cover the complexity of any passwords set on that realm.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (ELY-377) Add a SecurityFactory implementation to return a GSSCredential
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-377?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-377:
---------------------------------
Fix Version/s: 1.1.0.Beta6
(was: 1.1.0.Beta5)
> Add a SecurityFactory implementation to return a GSSCredential
> --------------------------------------------------------------
>
> Key: ELY-377
> URL: https://issues.jboss.org/browse/ELY-377
> Project: WildFly Elytron
> Issue Type: Task
> Components: Utils
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.1.0.Beta6
>
>
> This task is for a simple implementation that uses a JAAS call and the GSSAPI APIs to authenticate and obtain the GSSCredential.
> For completeness this utility should probably cover both the client side and server side use cases.
> Delegation however may call for a slightly different implement for the client side when running in a server.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (ELY-344) Review how clients use ModifiableRealmIdentity / ModifiableRealm
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-344?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-344:
---------------------------------
Fix Version/s: 1.1.0.Beta6
(was: 1.1.0.Beta5)
> Review how clients use ModifiableRealmIdentity / ModifiableRealm
> ----------------------------------------------------------------
>
> Key: ELY-344
> URL: https://issues.jboss.org/browse/ELY-344
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Realms
> Reporter: Darran Lofthouse
> Fix For: 1.1.0.Beta6
>
>
> This may be something we address in the subsystem but just raising here so we don't forget.
> Once we have a working set up with a realm which can be modified it seems unreasonable to expect the administrator to know exactly which credential types and names to use.
> This may need to be a few milestones away once we have the bulk integrated so the relationships are clear.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (ELY-355) HTTP Authentication Mechanism Testing
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-355?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-355:
---------------------------------
Fix Version/s: 1.1.0.Beta6
(was: 1.1.0.Beta5)
> HTTP Authentication Mechanism Testing
> -------------------------------------
>
> Key: ELY-355
> URL: https://issues.jboss.org/browse/ELY-355
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Testsuite
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.1.0.Beta6
>
>
> We don't want to create a full HTTP server but we should have a sufficient wrapper to test the HTTP authentication framework and test out specific mechanims.
> This will leave the Elytron Web project to smoke test integration and not focus on testing the actual mechanisms.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months