[ 
https://issues.apache.org/jira/browse/USERGRID-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158304#comment-14158304
 ] 

ASF GitHub Bot commented on USERGRID-225:
-----------------------------------------

GitHub user snoopdave opened a pull request:

    https://github.com/apache/incubator-usergrid/pull/82

    Fix USERGRID-225 by allowing ${blah} expressions in paths.

    This new regex allows paths to be specified like so:
    
        /users/${user}/**
    
    See also: https://issues.apache.org/jira/browse/USERGRID-225

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/snoopdave/incubator-usergrid usergrid-225

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-usergrid/pull/82.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #82
    
----
commit d087796277bb96d90e895284a987273852451852
Author: Dave Johnson <[email protected]>
Date:   2014-10-03T18:28:04Z

    Fix USERGRID-225 by allowing ${blah} expressions in paths.

----


> Portal will not allow $ in permission paths
> -------------------------------------------
>
>                 Key: USERGRID-225
>                 URL: https://issues.apache.org/jira/browse/USERGRID-225
>             Project: Usergrid
>          Issue Type: Bug
>          Components: Portal
>            Reporter: David Johnson
>
> On the Portal's ROLES page, when you click the Add Permission button, you 
> will see a New Permission dialog appear. If you try to use ${user} in the 
> Path field you will get an error that says "Path must begin with a slash, 
> path only allows: /, a-z, 0-9, dot, and dash, paths of the format: /path/ or 
> /path//path are not allowed"
> But, according to the docs, you can use ${user} in permissions path:
> "${user} Automatically sets the path segment to the UUID of the currently 
> authenticated user. For example, if you sent a request with a valid access 
> token for a user with UUID bd397ea1-a71c-3249-8a4c-62fd53c78ce7, the path 
> /users/${user} would be interpreted as 
> /users/bd397ea1-a71c-3249-8a4c-62fd53c78ce7, assigning the permission only to 
> that user entity."
> That is from:
> http://apigee.com/docs/api-baas/content/using-permissions
> (part of the docs not yet part of the Apache project)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to