I still don't get what is an admin API vs non-admin API.
Taking BPS as an example,
- Let's assume a client is writing a process-triggering app using the
provided APIs.
- They want to complete a user task by sending few users to be used as
candidate users in the next step.
- For thi
There is a way to do this. At the point of deploying the service, you have
to specify on which transports that service is exposed. This is similar to
the concept of exposing services on selected transports in Axis2.
On Fri, May 6, 2016 at 2:26 PM, Sagara Gunathunga wrote:
>
>
> On Thu, May 5, 20
On Thu, May 5, 2016 at 2:32 PM, Kishanthan Thangarajah
wrote:
> Another thing is, should we also work on exposing admin services on one
> listener (probably over https) and other user api's on different listener?
> May be we need to bring in some changes to MSF4J core to support this via
> OSGi l
Shall we come to a conclusion on which ports to use and whether all
servers use the same ports.
Regards
Nandika
On Thu, May 5, 2016 at 2:32 PM, Kishanthan Thangarajah
wrote:
> Another thing is, should we also work on exposing admin services on one
> listener (probably over https) and other use
Another thing is, should we also work on exposing admin services on one
listener (probably over https) and other user api's on different listener?
May be we need to bring in some changes to MSF4J core to support this via
OSGi level service properties and listener id's.
On Thu, May 5, 2016 at 7:39
Will you run admin stuff & user stuff on the same instances? At least
shouldn't our recommendation be that admin & user stuff have to be
separate, as a best practice?
On Wed, May 4, 2016 at 9:12 PM, Hasitha Aravinda wrote:
> Hi Manu,
>
> In my point of view, we have to decide it based on what AP
IMO It is an Admin API, Only an admin will need to know, who are the users
in a role. Process user will not require to know who are the users in a
group in user-store. Hmm.. Violating privacy ? :)
But process user only interest in getting user list for task delegation
(assignable user list for a t
So will getting a list of users for a role (in IS) a admin or user task?
On Wed, May 4, 2016 at 11:42 AM, Hasitha Aravinda wrote:
> Hi Manu,
>
> In my point of view, we have to decide it based on what API does and who
> are the actual users involve.
>
> In BPS, we have two sets of users: workflo
Hi Manu,
In my point of view, we have to decide it based on what API does and who
are the actual users involve.
In BPS, we have two sets of users: workflow participants and admin
user/devOps of the BPS. Based on these users we can categorized BPS APIs
into two sets.
- Admin APIs : There are f
How do we define an admin vs non-admin API?
Is getting list of users different from getting the list of processes?
A customer written UI may have to call both. We can argue that some things
are 100% admin eg: shutdown server. But to me this seems like an arbitrary
decision.
On Wed, May 4, 2016 a
Another thing, we need to consider exposing different ports for user APIs
and Admin APIs to have a clear separation. In C4 all user and admin APIs
exposed in 9443 and 9763. AFAIK this is not supported in current MSF4J OSGi
version.
Thanks,
Hasitha.
On Wed, May 4, 2016 at 9:26 AM, Nandika Jayaward
Hi All,
In all the carbon platform versions up to now, we used 9443, and 9763 ports
for admin services for all server products. Are we going to use the same
ports for C5.
Regards
Nandika
--
Nandika Jayawardana
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
___
12 matches
Mail list logo