Hi Sewmini, KeyManager configuration will be mainly used when integrating with a Third Party Authorization Server. Configuration specific to the external Authorization Server can be provided under KeyManager section. This is explained in doc link available at [1].
When clustering, you should only change the KeyValidator section. Gateway should know the location of the KeyValidator, so KeyValidator section of Gateway should be configured pointing to KeyValidator component. Store will be talking to KeyVaidator when creating OAuth clients. Therefore , Store should also know the location of KeyValidator. [1] https://docs.google.com/document/d/14y-1QmYsf2sm5n_5nFh8R4fePSxlcdMLO_J4FxTmWyc/edit On Thu, May 7, 2015 at 3:58 PM, Sewmini Jayaweera <sewm...@wso2.com> wrote: > Hi All, > > As per the offline discussion, Key validator server profile is acting as > Key manager when there is no third party Auth server is used. > > In the API Manager 1.9.0 pack <AM_HOME>/repository/conf/api-manager.xml > Key validator is enabled and Key manager is being commented out by > default. > > 1. Is there a reason why Key Manager configuration is there? > 2. If so when should we enable Key manager instead of Key validator? > 3. When we are clustering instead of changing Key manager configurations > should we change key validation configurations and what are the > configurations? > > Thanks & Regards, > Sewmini > > Sewmini Jayaweera > *Software Engineer - QA Team* > Mobile: +94 (0) 773 381 250 > sewm...@wso2.com > -- *Amila De Silva* WSO2 Inc. mobile :(+94) 775119302
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
