On Wed, Jul 17, 2013 at 5:17 PM, Samisa Abeysinghe <[email protected]> wrote:

> Why do you want to limit the use for a tier? What is the use case?
>

Right now, every subscriber can see & subscriber into every Tier
definition. But some business models require only users in certain roles to
see some Tiers during subscription.

eg:
John - Roles (Internal developer, App Tester)
Sam - Roles (third party developer)
Diane - Roles (third party tester)

Tier A - 10,000/hour
Tier B - 100/hour
Tier C - 500/hour

John is internal & trusted. He ia also an application tester. So its ok for
him to be allowed to subscribed to Tier A. But Sam is only a third party
developer. Allowing higher tier category for him is risky as he can load
the entire system. (or may be his role can be upgrade with a payment)





>
>
>
> On Wed, Jul 17, 2013 at 4:58 PM, Lakmali Baminiwatta <[email protected]>wrote:
>
>> Hi all,
>>
>> Currently in APIM, each subscriber can choose any tier when subscribing
>> to an API. There is no way to limit avaiable tiers to a particular user.
>> This feature will allow API publisher to define which tiers are visible for
>> which roles.
>>
>>
>> Changes - to publisher
>> =======================
>> A new UI is needed to map tiers & roles
>>
>> Changes - to store
>> ====================
>> Based on logged in user's roles, the list of tiers being presented @ the
>> point of subscription should be filtered.
>>
>>
>> Implication on existing subscriptions
>> ======================================
>> If the tier has already been used in existing subscription, we should not
>> allow role based restriction to be applied until those subscriptions are
>> removed.
>>
>> Would this be a good strategy?
>>
>> Looking forward for feedback, suggestions .
>>
>> Thanks,
>> Lakmali
>> --
>> Lakmali Baminiwatta*
>> *
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean.enterprise.middleware
>> mobile:  +94 71 2335936
>> blog : lakmali.com
>> *
>> *
>>
>> _______________________________________________
>> Architecture mailing list
>> [email protected]
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
> _______________________________________________
> Architecture mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
/sumedha
b :  bit.ly/sumedha
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to