There are some Thrift related configuration changes too. They are mentioned in [1].
[1] "Port offsetting the Thrift port in APIM" Thanks, Bhathiya On Sun, Jul 10, 2016 at 11:09 PM, Nuwan Dias <[email protected]> wrote: > Hi, > > As part of the configuration sanitization effort of the api-manager.xml > file, there have been several configuration changes that took place in API > Manager 2.0.0. The main objectives of this effort are to cleanup the > api-manager.xml file, remove unused configs and better structure the > document. The following lists the changes that were carried out. > > 1. Changes to the cache configurations. > > In version 1.10.0 and below, the api-manager.xml held cache configuration > of different caches. These caches configs were scattered all over the > api-manager.xml file and some config elements lacked consistency in their > naming. From version 2.0.0, all cache configs will fall under > the <CacheConfigurations> element. This element will hold all configs > related to enabling/disabling caches and the relevant configs to control > the cache timeouts. The following changes were made in the cache configs. > > Old Config New Config Description > <EnableGatewayKeyCache> <EnableGatewayTokenCache> Controls the Access > Token Cache on the Gateway > <EnableKeyMgtValidationInfoCache> <EnableKeyManagerTokenCache> Controls > the Access Token Cache on the Key Manager > > > 2. Changes to JWT configurations > > Old Config New Config Description > <APIConsumerAuthentication> <JWTConfiguration> The section that contains > the JWT configurations > <SecurityContextHeader> </JWTHeader> Specifies the name of the JWT header > <TokenGeneratorImpl> <JWTGeneratorImpl> Specifies the name of the class > that generates the JWT > > > 3. Changes to Analytics configurations. > > Old Config New Config Description > <APIUsageTracking> <Analytics> The section that contains the Analytics > configurations > > In addition to the above changes, a new section was introduced to hold > OAuth2.0 related API Manager specific configurations. This new section > brings together OAuth related configs which were earlier scattered over the > api-manager.xml file. This is what it contains now. > > <OAuthConfigurations> > <RemoveOAuthHeadersFromOutMessage>true</RemoveOAuthHeadersFromOutMessage> > <ApplicationTokenScope>am_application_scope</ApplicationTokenScope> > <ScopeWhitelist> > <Scope>^device_.*</Scope> > <Scope>openid</Scope> > </ScopeWhitelist> > <TokenEndPointName>/oauth2/token</TokenEndPointName> > > <RevokeAPIURL>https://${carbon.local.ip}:${https.nio.port}/revoke</RevokeAPIURL> > <EncryptPersistedTokens>false</EncryptPersistedTokens> > </OAuthConfigurations> > > Thanks, > NuwanD. > > -- > Nuwan Dias > > Technical Lead - WSO2, Inc. http://wso2.com > email : [email protected] > Phone : +94 777 775 729 > -- *Bhathiya Jayasekara* *Senior Software Engineer,* *WSO2 inc., http://wso2.com <http://wso2.com>* *Phone: +94715478185* *LinkedIn: http://www.linkedin.com/in/bhathiyaj <http://www.linkedin.com/in/bhathiyaj>* *Twitter: https://twitter.com/bhathiyax <https://twitter.com/bhathiyax>* *Blog: http://movingaheadblog.blogspot.com <http://movingaheadblog.blogspot.com/>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
