[JBoss JIRA] (ISPN-10375) Simple tutorials doc ascii doc style
by Katia Aresti (Jira)
[ https://issues.jboss.org/browse/ISPN-10375?page=com.atlassian.jira.plugin... ]
Katia Aresti updated ISPN-10375:
--------------------------------
Description: simple tutorials part of the infinispan web site would benefit of being ascii doc style documentation (was: simple tutorials part of the infinispan web site would benefit of being ascii doc style doctumentation)
> Simple tutorials doc ascii doc style
> ------------------------------------
>
> Key: ISPN-10375
> URL: https://issues.jboss.org/browse/ISPN-10375
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation-Core
> Reporter: Katia Aresti
> Assignee: Donald Naro
> Priority: Minor
>
> simple tutorials part of the infinispan web site would benefit of being ascii doc style documentation
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 10 months
[JBoss JIRA] (ISPN-9704) REST fine grained security support
by Gustavo Fernandes (Jira)
[ https://issues.jboss.org/browse/ISPN-9704?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-9704:
------------------------------------
Description:
Currently the REST server requires authentication but does not offer authorization capabilities. The new REST API described in ISPN-8535 requires that invocations on resources can be restricted on a per user/role basis.
Examples:
/GET on /rest/v2/{cacheName} should be allowed for all authenticated users
/POST on /rest/v2/{cacheName} should be restricted to users having the ADMIN role
Role MONITOR could have permission only to do GET on /rest/v2/caches/mycache/stats
was:
Currently the REST server requires authentication but does not offer authorization capabilities. The new REST API described in ISPN-8535 requires that invocations on resources can be restricted on a per user/role basis.
Examples:
/GET on /rest/v2/{cacheName} should be allowed for all authenticated users
/POST on /rest/v2/{cacheName} should be restricted to users having the ADMIN role
> REST fine grained security support
> ----------------------------------
>
> Key: ISPN-9704
> URL: https://issues.jboss.org/browse/ISPN-9704
> Project: Infinispan
> Issue Type: Feature Request
> Reporter: Gustavo Fernandes
> Priority: Major
>
> Currently the REST server requires authentication but does not offer authorization capabilities. The new REST API described in ISPN-8535 requires that invocations on resources can be restricted on a per user/role basis.
> Examples:
> /GET on /rest/v2/{cacheName} should be allowed for all authenticated users
> /POST on /rest/v2/{cacheName} should be restricted to users having the ADMIN role
> Role MONITOR could have permission only to do GET on /rest/v2/caches/mycache/stats
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 10 months
[JBoss JIRA] (ISPN-8736) REST endpoint authorization
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-8736?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8736:
----------------------------------
Sprint: DataGrid Sprint #30
> REST endpoint authorization
> ---------------------------
>
> Key: ISPN-8736
> URL: https://issues.jboss.org/browse/ISPN-8736
> Project: Infinispan
> Issue Type: Enhancement
> Components: REST, Security, Server
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
>
> The REST endpoint does not use the authenticated user to access authz caches. We need to:
> - integrate with the ServerAuthenticationProvider as used by the Hot Rod endpoint so that we can use security callbacks and retrieve a fully populated subject (including groups). This should ultimately connect with Elytron.
> - add SecurityActions within the rest code
> - Return 403 forbidden where needed
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 10 months