Sanjiva, Sameera, Asanka and myself had a chat regarding this use case and
following are the notes of it for others' information.
- It is not necessary to invite anyone to be a user in your tenant. If
you are the tenant admin, you can simply add the user to your tenant and
inform that user.
- For an internal deployment, adding users is not necessary since
we'll be pointing to the organization's LDAP. So, all the users
are there.
We only have to assign them to different apps.
- For the cloud, if you want to add someone, you simply add him/her
and let her know the credentials.
- If you want you can have a feature of notifying that user via
email. But this is not needed for the nearest release.
- Assigning users (amila) from other tenant (foo.com) to your tenant (
bar.com)
- Although we have agreed to create a user in my tenant am...@bar.com to
achieve this scenario, Sanjiva wants to do this via resource level
permissions.
- So, this feature will not be available for the nearest release.
When we start addressing this feature, we'll have to figure out how to do
it.
- Also discussed about OT users to login via a community tenant (this
has been already discussed in the previous review)
- We'll use a separate login page for this. When we create this
community tenant, we'll have to copy a user-mgt.xml which points
to the OT
LDAP.
Regards,
AmilaM.
On Mon, Sep 2, 2013 at 2:52 PM, Sameera Perera <samee...@wso2.com> wrote:
> The scenario I described is based on that I'm the first 'sameera' from
> wso2.com signing up for your tenant. Other sameera(s) have not signed up
> for the tenant but, they exist within the organization with wso2.comemail
> addresses. This is a probable use case in the cloud as well as when
> an LDAP is not linked in a private deployment; i.e. aPaaS/AF doesn't know
> about IDs that exist outside of it's database.
>
>
> On Mon, Sep 2, 2013 at 2:46 PM, Asanka Dissanayake <asan...@wso2.com>wrote:
>
>> Hi Smaeera,
>> Please find my comments in line.
>>
>>
>>
>> On Mon, Sep 2, 2013 at 2:42 PM, Sameera Perera <samee...@wso2.com> wrote:
>>
>>> Hi Asanka,
>>> While this is possible, I have concerns about doing this. E.g.
>>> You invite me to wso2.com tenant.
>>> When I follow the confirmation link, I have an option to provide my own
>>> username. So, I pick 'sameera'.
>>>
>> When you select a user name it will be assigned depending on the
>> availability. if there is a sameera in wso2.com already you are not
>> allowed to select it.
>>
>>> Now my tenant login is sameeraATwso2.com (where as my email is
>>> sameerapATwso2.com). Now, if actual sameeraATwso2.com wants to signup, he
>>> needs to use an alternate address.
>>>
>>> There are few solutions to this. We can discuss f2f.
>>>
>>>
>>> On Mon, Sep 2, 2013 at 1:13 PM, Asanka Dissanayake <asan...@wso2.com>wrote:
>>>
>>>> Hi,
>>>> @ sameera,
>>>> got the point. thanks for the clarification.
>>>> we have an alternative. But I don't know whether it is expensive.In the
>>>> tenant registration page we allow user to choose user name for the tenant
>>>> admin.Can't we allow same thing for the user .
>>>> It's like this,
>>>> When a user is invited as a user of the tenant , he gets an email which
>>>> contains the confirmation link.upon the click he is redirected to the page
>>>> for user registration where he can choose a user name . depending on the
>>>> availability suppose he selected user name as "asanka88" for the tenant
>>>> foo. Then his login name would be "asank...@foo.com".
>>>> WDYT?
>>>>
>>>> @ gayan,
>>>> I think answer for your questionis in the above answer.
>>>> cheers!!!
>>>> Asanka D
>>>>
>>>>
>>>>
>>>>
>>>> On Mon, Sep 2, 2013 at 12:57 PM, Gayan Dhanushka <gay...@wso2.com>wrote:
>>>>
>>>>> Hi Asanka,
>>>>>
>>>>> I would like to make a point that this is different from something
>>>>> like inviting an existing user to an app as a develpoer by the app owner.
>>>>> In that case the user is already there. As per my thinking this is a whole
>>>>> different scenario. I would like to know whether this user is already
>>>>> registered under the same organization, so that adding a user to a tenant
>>>>> points to adding a user who is already there in an organization to the
>>>>> same
>>>>> organization's appfac tenant?
>>>>>
>>>>> Thanks!
>>>>> GayanD
>>>>>
>>>>>
>>>>> On Mon, Sep 2, 2013 at 12:28 PM, Sameera Perera <samee...@wso2.com>wrote:
>>>>>
>>>>>> Ideally the scenario you describe should work. But, if you add
>>>>>> x...@bar.com to your foo.com domain, how do you know to log him in to
>>>>>> foo.com from the login page? What if bar.com is a tenant as well?
>>>>>> How do you know where to log him in?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Sep 2, 2013 at 12:15 PM, Asanka Dissanayake <asan...@wso2.com
>>>>>> > wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>> @ shiro
>>>>>>> #1 and #2 already there. will look in to #3.
>>>>>>>
>>>>>>> @sameera,
>>>>>>> so in that case, we are not gonna support private email addresses.
>>>>>>> For example I need to use aPaaS and create an organization called foo,
>>>>>>> and
>>>>>>> i dont't have @foo.com email adresses. I want to add users to the
>>>>>>> tenant with their private email addresses. I think this scenario fails
>>>>>>> if
>>>>>>> we put a restriction on the email address.
>>>>>>>
>>>>>>> If I am missing the point can you please explain me the reason for
>>>>>>> not allowing use arbitrary email addresses?
>>>>>>>
>>>>>>> cheers!!
>>>>>>> Asanka D
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Sep 2, 2013 at 11:53 AM, Sameera Perera
>>>>>>> <samee...@wso2.com>wrote:
>>>>>>>
>>>>>>>> Hi Asanka,
>>>>>>>>
>>>>>>>> For the cloud, can you confirm that we will not support adding
>>>>>>>> user with any arbitrary email address for this phase?
>>>>>>>> I.e. Only users with @tenantdomain email addresses can be added.
>>>>>>>> Can you confirm?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Sep 2, 2013 at 11:48 AM, Asanka Dissanayake <
>>>>>>>> asan...@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>> User story for adding a user to a tenant is as follows.
>>>>>>>>>
>>>>>>>>> 1- tenant admin enter the email of the user(not in the LDAP yet)
>>>>>>>>> and select a role.
>>>>>>>>> 2- then tenant admin invite the user.
>>>>>>>>> 3- then user receives an email containing confirmation link.
>>>>>>>>> 4- upon the confirmation user is added to the tenant domain.
>>>>>>>>>
>>>>>>>>> According to the offline chat had with Dimuthu, we came to a
>>>>>>>>> conclusion that there is no point of adding a user to the tenant
>>>>>>>>> domain
>>>>>>>>> before sending the email unless it's a user within the
>>>>>>>>> organization.But
>>>>>>>>> when it comes to cloud, any one wouldn't like to be a developer,qa of
>>>>>>>>> an
>>>>>>>>> application without his permission/confirmation.
>>>>>>>>>
>>>>>>>>> Please give comments on the above user story. I need to get this
>>>>>>>>> finalized to start implementations. Quick reply s are highly
>>>>>>>>> appreciated.
>>>>>>>>>
>>>>>>>>> cheers!!
>>>>>>>>> Asanka D
>>>>>>>>> --
>>>>>>>>>
>>>>>>>>> *Asanka Dissanayake
>>>>>>>>> Software Engineer*
>>>>>>>>> *WSO2 Inc. - lean . enterprise . middleware | wso2.com*
>>>>>>>>> *
>>>>>>>>> email: asan...@wso2.com <ruch...@wso2.com>, blog:
>>>>>>>>> cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com mobile:
>>>>>>>>> +94 71 8373821*
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> ------------------------------
>>>>>>>>
>>>>>>>> *Sameera Perera*
>>>>>>>> Senior Manager, Cloud Technology Group
>>>>>>>> gtalk: samee...@wso2.com
>>>>>>>> *WSO2, Inc.* <http://wso2.com/>
>>>>>>>> lean.enterprise.middleware
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> *Asanka Dissanayake
>>>>>>> Software Engineer*
>>>>>>> *WSO2 Inc. - lean . enterprise . middleware | wso2.com*
>>>>>>> *
>>>>>>> email: asan...@wso2.com <ruch...@wso2.com>, blog:
>>>>>>> cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com mobile: +94
>>>>>>> 71 8373821*
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> ------------------------------
>>>>>>
>>>>>> *Sameera Perera*
>>>>>> Senior Manager, Cloud Technology Group
>>>>>> gtalk: samee...@wso2.com
>>>>>> *WSO2, Inc.* <http://wso2.com/>
>>>>>> lean.enterprise.middleware
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Dev mailing list
>>>>>> Dev@wso2.org
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Gayan Dhanushka
>>>>> Software Engineer
>>>>> WSO2 Inc.
>>>>> http://wso2.com
>>>>>
>>>>> Mobile : 0716662327
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> *Asanka Dissanayake
>>>> Software Engineer*
>>>> *WSO2 Inc. - lean . enterprise . middleware | wso2.com*
>>>> *
>>>> email: asan...@wso2.com <ruch...@wso2.com>, blog:
>>>> cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com mobile: +94
>>>> 71 8373821*
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> ------------------------------
>>>
>>> *Sameera Perera*
>>> Senior Manager, Cloud Technology Group
>>> gtalk: samee...@wso2.com
>>> *WSO2, Inc.* <http://wso2.com/>
>>> lean.enterprise.middleware
>>>
>>>
>>>
>>
>>
>> --
>>
>> *Asanka Dissanayake
>> Software Engineer*
>> *WSO2 Inc. - lean . enterprise . middleware | wso2.com*
>> *
>> email: asan...@wso2.com <ruch...@wso2.com>, blog:
>> cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com mobile: +94
>> 71 8373821*
>>
>
>
>
> --
>
> ------------------------------
>
> *Sameera Perera*
> Senior Manager, Cloud Technology Group
> gtalk: samee...@wso2.com
> *WSO2, Inc.* <http://wso2.com/>
> lean.enterprise.middleware
>
>
>
> _______________________________________________
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com
Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
