Cisco Bug: CSCta49316 - .NET PEP assemblies cache provider looks for wrong file
Feb 22, 2014
- Cisco Policy Administration Point
Known Affected Releases
Symptom: Com.Cisco.Epm.AuthorizationManagerFactory.GetInstance allows you to pass in path to a configuration file, however if you enable caching with Com.Cisco.Epm.Cach.CaheProvider, the CacheProvider always attempts to read from the file "pep_config.xml" regardless of what path you'd passed to GetInstance Conditions: This is observed when we enable caching to true in pep_config.xml and specify the path in GetInstance method for Dot Net API's.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases