Hi Ruwan,
IMHO, for App Manager users it'll be useful to have set of default roles
given that the permissions are assigned accurately.
We reported many issues in this area assuming the following is the expected
behavior.
*Transition Process* *Allowed Roles* *Allowed Actions* Creating a new
Hi,
FYI, Here is how Mobile Apps works.
Roles
1. Intermal/Publisher
2. Internal/Reviewer
3. admin (admin has ability to perform all operations below)
-
*Main Flow*
*Publisher*
1. Publisher *create* the app
2. App
Hi,
Need some clarification regarding the issue - [1].
In super tenant mode all the default roles can be seen once we login to
carbon console(Internal/everyone, Internal/publisher,
Internal/reviewer, Internal/subscriber,
admin roles) . But in tenant mode, when we initially log in to admin
Hi Thilini,
I think it is coming form ES. In publisher those roles are created when the
admin user first login to the publisher. +1 for Dinusha's suggestion
On Fri, Feb 6, 2015 at 2:25 PM, Dinusha Senanayaka dinu...@wso2.com wrote:
Hi Thilini,
On Fri, Feb 6, 2015 at 2:07 PM, Thilini
Hi Thilini,
The internal/store role is pretty much obsolete AFAIK. However there are
specific validations on the roles i've listed below .
intermal/publisher - Can create Apps but cannot publish
internal/reviewer - Ones, publisher submits for an app to be published,
reviewer permission is needed
Hi all,
There are several bugs reported regarding the permission issues of default
roles in App Manager. In order to fix and resolve them, we need to clarify
what are the exact usage and permissions which should assigned with those
roles.
The roles which were subjected to permission issues are
