...
| Time | Item | Who | Notes | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Does the generated RST meet the requirements? Can we close the task? | ||||||||||||
| Cassandra Clustering in OOM |
| ||||||||||||
| MSB Configuration |
| ||||||||||||
| AAF | James Forsyth | Do we use AAF in Beijing? Will MSB broker authentication and authorization requests to AAF on behalf of AAI? According to Huabing, there is a plugin to do the authorization before the request is passed to AAI. Huabing will talk to AAF to see if this approach is reasonable for Beijing. If MSB does it, AAI's role would be to define the user set and roles in the AAF interface, and the MSB will send URI + HTTP method at runtime to do the AA functions. If MSB does not do it, then AAI will be responsible for configuring the CADI plugin in Jetty and do the authorization for ourselves. If we don't use AAF then we'll need to implement something similar to the ECOMP policy subsystem. Huabing Zhao: After looking into the AAF documentation, it seems that AAF has its own permission model(triple of type, instance, and action) which can not be directly mapped to http method and resource. So I don't see how MSB could do the authorization on behalf of service requester. | |||||||||||
| Backlog grooming | Jira Backlog |
...