Hi all, Currently we have implemented Resource Registration endpoint and a Permission endpoint for protection API in UMA 2.0. There are following database considerations for UMA API during the implementation.
1. The existing IDN_OAUTH_SCOPE table is used by the API Manager when registering scopes and DISPLAY_NAME field is defined as a mandatory (NOT_NULL CONSTRAINT). But according to UMA specification DISPLAY NAME is not defined. So that for UMA,we think it's better to use a separate table with mandatory and optional properties given in the specification, rather enforcing to invoke UMA API with DISPLAY_NAME What Do You Think? 2. Currently in scope table, we used auto generated Id as the unique id for scope and that id is used to invoke all the crud operations. Will it be fine to invoke the APIs using the auto incremented ID or we need to use a UUID for that? 3. There is many to many relationship between IDN_RESOURCE and IDN_OAUTH_SCOPE. It's better to have separate references (child) table (IDN_RESOURCE_SCOPE as given in the diagram) to have mapping between SCOPE_ID and RESOURCE_ID. Thanks. Kind Regards. > > -- Isuri Anuradha Trainee Software Engineer | WSO2 Emaii : is...@wso2.com Mobile : +94775941280 web :http://wso2.com <http:///wso2.com>
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
