Hi Aarushi, This is nice. Few questions/comments:
* For createTentant API looks like client has to provide a tenantId, instead can the server generate and return a unique tenantId? * within getCredentials API call, instead of oauthCliendId and oauthClientSecret, can you please make them iamClientId and iamClientSecret? To confirm with OAuth 2.0 Dynamic Client Registration Protocol, can you also add additional client metadata like client name, client uri, logo uri, scope, contacts? Refer: https://tools.ietf.org/html/rfc7591 <https://tools.ietf.org/html/rfc7591> Cheers, Suresh > On Nov 18, 2019, at 3:13 PM, Bisht, Aarushi <[email protected]> wrote: > > Hi All, > > For the past couple of days I have been experimenting with swagger > specification and swagger hub. I have generated API specification for Tenant > Profile service. These are public APIs which will be used by Custos clients > to register their tenants and obtain tenant credentials. > > I have attached the documentation to the mail. It also contains sample SDK > samples in different languages. It can be viewed by opening the index.html > file in the browser. Please let me know if someone has a suggestion of > exposing any other public API or modify existing ones or modification of the > API models. > > > Thanks & Regards, > Aarushi Bisht > > > <html2-documentation-generated.zip>
