Hi, Please find the answers inline.
On Wed, Feb 8, 2017 at 10:04 AM, Abimaran Kugathasan <[email protected]> wrote: > HI Pubudu, > > 1. Who will be responsible for creating these labels? I guess, it should > be created from Admin Portal and those labels should be propagated to > store, publisher, gateway. > Considering some of the ideas we received thought of changing the behaviour. We can dynamically add labels. When we are starting up the gateway nodes we have to provide a label such as public, private,etc. These labels will be saved in the database. In the publisher, these labels will be displayed when creating an API. Then you can select which gateway you need to use. This will provide the flexibility to add different gateway envioronments. Additionally, if you need to serve an API from the newly created gateway, then you need to update the API with the newly created gateway label. You do not need to define any labels in any of the configuration files. > 2. How do you restrict the users invoking from different gateway > environments? Allowing to invoke from provided gateway environment. We > can't validate from Key Manager since Key Manager can be anything which > adheres OAuth 2 spec. They don't need to know anything related labels. > > We do not restrict any invocations. If the users can send requests to the gateway, those will be served. > 3. How do you map users to labels? Who will map the users? If an admin > does this, on which basis labels will be assigned to users? > We are not mapping any labels to the users by default. But we are providing an extension point where users can select for labels. It could be based on the roles, headers, etc. From this you will be able to restrict some of the labels to particular users. For an example, internal users who belongs to engineering group will see public and private labels and external users will see public label. > 4. We can't let the users create label because it reflects the internal > gateway deployment pattern. > As I mentioned above, labels are created based on the gateway deployment. > > > On Wed, Feb 8, 2017 at 5:03 AM, Ishara Cooray <[email protected]> wrote: > >> Hi Pubudu, >> >> What will be the behavior when an api is updated >> >> 1. From API publisher UI >> 2. From the api artifact itself(if it is allowed). >> >> Basically, when an API is updated a message will be published to the broker and gateways will receive the event if gateway is up and running. If the gateway is serving requests on demand, it will only update the API artifact once it receives another request. Until then, it will not update the artifact. Thank you! -- *Pubudu Gunatilaka* Committer and PMC Member - Apache Stratos Software Engineer WSO2, Inc.: http://wso2.com mobile : +94774078049 <%2B94772207163>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
