Yes, i also think same. Using identity server as key manager would be a
better choice as we can get both API and IS fixes via WUM.
But we need to have some solution for all in one scenario. Other than that
any HA deployment have key manager and we can easily replace it with is as
KM and use those features.
On Mon, Feb 5, 2018 at 12:10 PM, Nuwan Dias <nuw...@wso2.com> wrote:
> As mentioned on the subject itself, these are Identity Management and
> Identity Governance features. They don't closely tie in with API
> Management. Therefore I think its fine to recommend IS for those kind of
> use cases.
> Installing these features to APIM at this point in time is also a problem
> due to its roadmap with 3.0. If we install these features into APIM users
> will see these as first class features of our APIM offering, they won't see
> this as something coming from IS. Which means that users would expect the
> same set of features on 3.0 as well. Therefore I would be -1 to installing
> these features on APIM.
> On Mon, Feb 5, 2018 at 9:49 AM, Asela Pathberiya <as...@wso2.com> wrote:
>> Hi All,
>> There are several customers/users who are looking for $subject with
>> APIM. Specially following features
>> 1. Account lock/disable
>> 2. Password/Account recovery
>> 3. Password policies
>> We are usually not recommending the feature installation. Therefore,
>> shall we ship these features by default with APIM.
>> However, we can suggests to use WSO2IS as KM, but we need to consider on
>> 1. Cost on running WSO2IS (infra cost)
>> 2. All in one deployment
>> 3. First impression on the IAM feature list of APIM.
>> WDYT ?
>> Thanks & Regards,
>> Mobile : +94 777 625 933 <+94%2077%20762%205933>
>> +358 449 228 979
> Nuwan Dias
> Software Architect - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729 <077%20777%205729>
Mobile : +94713068779
Architecture mailing list