-
Bug
-
Resolution: Unresolved
-
None
-
None
-
true
You should be able to specify multiple role-names by using comma separated values accordingly this example in the documentation:
<seraph-paths>
<!-- You can configure any number of path elements -->
<path name="admin">
<url-pattern>/admin/*</url-pattern>
<role-name>myapp-administrators, myapp-owners</role-name>
</path>
</seraph-paths>
However, the user must be part of all roles specified in the configuration since the comma is like a "AND" logic operator.
This improvement to solely created for the option to change the comma logic to be something like an "OR" semantic instead, which means that an user who is part of the 'myapp-owners' role only like the example above will be correct.
[SER-185] Seraph configuration fails when I try to specify more than one group for role-name
| Key | Original: CONF-27793 | New: SER-185 |
| Project | Original: Confluence [ 10470 ] | New: atlassian-seraph [ 10480 ] |
| Affects Version/s | Original: 4.2.3 [ 26215 ] | |
| Workflow | Original: New Confluence Default Workflow [ 477530 ] | New: reviewflow [ 537858 ] |
| Status | Original: New [ 10034 ] | New: Open [ 1 ] |
| Issue Type | Original: Improvement [ 4 ] | New: Bug [ 1 ] |
Anatoli Kazatchkov [Administrative Account]
made changes -
| Workflow | Original: Confluence Default Workflow [ 457368 ] | New: New Confluence Default Workflow [ 477530 ] |
| Description |
Original:
You should be able to specify multiple role-names by using comma separated values [accordingly this example in the documentation|http://docs.atlassian.com/atlassian-seraph/latest/services.html]:
{code} <seraph-paths> <!-- You can configure any number of path elements --> <path name="admin"> <url-pattern>/admin/*</url-pattern> <role-name>myapp-administrators, myapp-owners</role-name> </path> </seraph-paths> {code} However, the user must be part of all roles specified in the configuration since the comma is like a "AND" logic operator. This improvement to solely created for the option to change the comma logic to be something like an "OR" semantic instead, which means that an user who is part of the 'myapp-owners' role only like the example above will be correct. |
New:
You should be able to *specify multiple* role-names by using comma separated values [accordingly this example in the documentation|http://docs.atlassian.com/atlassian-seraph/latest/services.html]:
{code} <seraph-paths> <!-- You can configure any number of path elements --> <path name="admin"> <url-pattern>/admin/*</url-pattern> <role-name>myapp-administrators, myapp-owners</role-name> </path> </seraph-paths> {code} However, the user must be part of all roles specified in the configuration since the comma is like a "AND" logic operator. This improvement to solely created for the option to change the comma logic to be something like an "OR" semantic instead, which means that an user who is part of the 'myapp-owners' role only like the example above will be correct. |
| Description |
Original:
You should be able to specify multiple role-names by using comma separated values accordingly this example:
{code} <seraph-paths> <!-- You can configure any number of path elements --> <path name="admin"> <url-pattern>/admin/*</url-pattern> <role-name>myapp-administrators, myapp-owners</role-name> </path> </seraph-paths> {code} However, the user must be part of all roles specified in the configuration since the comma is like a "AND" logic operator. This improvement to solely created for the option to change the comma logic to be something like an "OR" instead, which means that an user who is part of the 'myapp-owners' role only like the example above will be correct. |
New:
You should be able to specify multiple role-names by using comma separated values [accordingly this example in the documentation|http://docs.atlassian.com/atlassian-seraph/latest/services.html]:
{code} <seraph-paths> <!-- You can configure any number of path elements --> <path name="admin"> <url-pattern>/admin/*</url-pattern> <role-name>myapp-administrators, myapp-owners</role-name> </path> </seraph-paths> {code} However, the user must be part of all roles specified in the configuration since the comma is like a "AND" logic operator. This improvement to solely created for the option to change the comma logic to be something like an "OR" semantic instead, which means that an user who is part of the 'myapp-owners' role only like the example above will be correct. |