You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Toby Stevens (JIRA)" <ji...@apache.org> on 2009/02/06 15:11:59 UTC
[jira] Created: (JSEC-55) Add Authenticating Cache to
AuthenticatingRealm
Add Authenticating Cache to AuthenticatingRealm
-----------------------------------------------
Key: JSEC-55
URL: https://issues.apache.org/jira/browse/JSEC-55
Project: JSecurity
Issue Type: Improvement
Components: Caching, Realms
Environment: Any
Reporter: Toby Stevens
Fix For: 1.0
Stateless clients would benefit from an authentication cache.
For example if a stateless client may make several authentication requests within a few seconds.
Ideally the cache timeouts would be different. For example i might want to sent the Authentication cache to 30 seconds, but the Authorization cache to longer.
(From previous email to Les)
I created a Realm that authenticates against a URL, if the user has
access. The problem is that we have a stateless client [maven2] that
connects to our server[Nexus], and needs to authenticate each time.
This means the same user needs to authenticate 9+ times in a few
seconds (for a single task).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Moved: (KI-58) Add Authenticating Cache to
AuthenticatingRealm
Posted by "Alan Cabrera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KI-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Cabrera moved JSEC-55 to KI-58:
------------------------------------
Fix Version/s: (was: 1.0)
Component/s: (was: Realms)
(was: Caching)
Key: KI-58 (was: JSEC-55)
Project: Ki (was: JSecurity)
> Add Authenticating Cache to AuthenticatingRealm
> -----------------------------------------------
>
> Key: KI-58
> URL: https://issues.apache.org/jira/browse/KI-58
> Project: Ki
> Issue Type: Improvement
> Environment: Any
> Reporter: Toby Stevens
> Assignee: Jeremy Haile
>
> Stateless clients would benefit from an authentication cache.
> For example if a stateless client may make several authentication requests within a few seconds.
> Ideally the cache timeouts would be different. For example i might want to sent the Authentication cache to 30 seconds, but the Authorization cache to longer.
> (From previous email to Les)
> I created a Realm that authenticates against a URL, if the user has
> access. The problem is that we have a stateless client [maven2] that
> connects to our server[Nexus], and needs to authenticate each time.
> This means the same user needs to authenticate 9+ times in a few
> seconds (for a single task).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (JSEC-55) Add Authenticating Cache to
AuthenticatingRealm
Posted by "Jeremy Haile (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSEC-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Haile reassigned JSEC-55:
--------------------------------
Assignee: Jeremy Haile
> Add Authenticating Cache to AuthenticatingRealm
> -----------------------------------------------
>
> Key: JSEC-55
> URL: https://issues.apache.org/jira/browse/JSEC-55
> Project: JSecurity
> Issue Type: Improvement
> Components: Caching, Realms
> Environment: Any
> Reporter: Toby Stevens
> Assignee: Jeremy Haile
> Fix For: 1.0
>
>
> Stateless clients would benefit from an authentication cache.
> For example if a stateless client may make several authentication requests within a few seconds.
> Ideally the cache timeouts would be different. For example i might want to sent the Authentication cache to 30 seconds, but the Authorization cache to longer.
> (From previous email to Les)
> I created a Realm that authenticates against a URL, if the user has
> access. The problem is that we have a stateless client [maven2] that
> connects to our server[Nexus], and needs to authenticate each time.
> This means the same user needs to authenticate 9+ times in a few
> seconds (for a single task).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.