You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Les Hazlewood (JIRA)" <ji...@apache.org> on 2011/04/12 02:49:05 UTC

[jira] [Updated] (SHIRO-73) Add Authentication Caching to AuthenticatingRealm

     [ https://issues.apache.org/jira/browse/SHIRO-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Les Hazlewood updated SHIRO-73:
-------------------------------

    Issue Type: New Feature  (was: Improvement)
       Summary: Add Authentication Caching to AuthenticatingRealm  (was: Add Authenticating Cache to AuthenticatingRealm)

> Add Authentication Caching to AuthenticatingRealm
> -------------------------------------------------
>
>                 Key: SHIRO-73
>                 URL: https://issues.apache.org/jira/browse/SHIRO-73
>             Project: Shiro
>          Issue Type: New Feature
>         Environment: Any
>            Reporter: Toby Stevens
>            Assignee: Les Hazlewood
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira