On Wed, Sep 3, 2014 at 9:02 PM, Chamila Adhikarinayake <chami...@wso2.com> wrote:
> Hi all, > I'm creating user self signup feature for tenant store in API Manager. > Current api manager provides only self signup facility for carbon.super > store. To add tenant users, tenant admin has to manually add it through the > carbon console. > > Following parts will be implemented > > *UI changes* (see attached images) > > 1. enable the sign-up button for tenant user store > 2. add the domain name extension for the user name field in the user > registration form. (this is appended to the user name) > > *User roles for tenants * > > Tenant signup configuration will be moved to the registry location > '/_system/governance/repository/identity/sign-up-config'. This part is > already implemented by Shariq for a IS component(See discussion in the > thread "Provide support for self signup for tenants' APIStores" for more > info on the configuration). But this resource needed to be created > manually. So as a part of the implementation, This resource will be added > with default values when creating a tenant. Default value will be > > <SelfSignUp> > <SignUpDomain>PRIMARY</SignUpDomain> > <SignUpRole> > <RoleName>subscriber</RoleName> > <IsExternalRole>false</IsExternalRole> > </SignUpRole> > </SelfSignUp> > > > *Modification to current work-flow for tenant sign-up. * > > The current implemented method does not work when > UserSignUpWSWorkflowExecutor is used in the work-flow. this can be only > used with tenants signups for superuser. Existing code uses configuration > in the carbon super user's registry entry > '/_system/governance/apimgt/applicationdata/workflow-extensions.xml' for > tenants as well ( see jsFunction_addUser() in > org.wso2.carbon.apimgt.hostobjects.APIStoreHostObject class. ). When > registering a tenant user for different tenant, configuration in the > tenant's workflow-extensions.xml needed to be used. > > I have implemented basic functionality[1] as requested by AmilaM (Users > can signup for tenant stores. But Tenant admin has to manually add the > registry entry with user roles to the given location. If this entry is not > there, a default 'identity' user role is assigned to the user. Only > UserSignUpSimpleWorkflowExecutor for the workflow can be used with this. If > UserSignUpWSWorkflowExecutor is used to connect to the BPS, the tenant > approval tasks are not created properly) > Do we know the reason for the tasks of the BPS not being created when the UserSignUpWSWorkflowExecutor is used? We will need to dig into that IMO. > > [1] https://wso2.org/jira/browse/APIMANAGER-2785 > > Comments are highly appreciated > Thanks, > Chamila. > > -- > Regards, > Chamila Adhikarinayake > Software Engineer > WSO2, Inc. > Mobile - +94712346437 > Email - chami...@wso2.com > -- Nuwan Dias Associate Tech Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
