Releases: predix/acs
Release 5.0.1
Merge pull request #167 from predix/release-5.0.1 Release 5.0.1
Release 5.0.0
With this release caching could be enabled for external attribute connectors. Caching interval is configurable with minimum of 30 minutes. Default caching interval is 8 hours. Please refer to ACS API docs on Predix.io for more details
Release 4.8.1
New Features:
Zipkin Integration
ACS now utilizes spring-cloud-sleuth as a distributed tracing system. This helps to gather timing data needed to troubleshoot latency problems across services.
JSON log format
Log format has been updated to use JSON, with some additional fields for tenant(tnt), deployment id(pmt), instance id(inst) and zipkin trace id ('corr'). Example:
{"time":"2017-06-26T18:21:30.114+0000","tnt":null,"corr":null,"appn":null,"dpmt":null,"inst":null,"tid":"main","mod":"Acs RequestContextBuilder JPA Repositories Initialized"}
Health Check
Navigating to /health
endpoint as a privileged user now gives a detailed breakdown of the current health of ACS and it's dependent services.
Improvements:
Decision Caching
ACS decision caching has been updated to allow eviction of invalidation keys (subject, resource id, policy set), in addition to the cached decisions. Note: With this change, Redis must be setup with an eviction policy of allkeys-lru
.
Release 4.7.1
Improved thread safety and performance of encryption and decryption of client secrets for attribute adapters
Release 4.7.0
New Features:
Attribute connectors
With this release, ACS zones could be configured during policy evaluation to reference attributes of protected resource and currently authenticated user from external sources, e.g. Predix Asset. Changes in attribute values in external source will not reflect in ACS policy evaluation in real-time. Caching interval for external attributes is configurable with minimum of 30 minutes. Default caching interval is 8 hours. If the system is unable to get attributes within the refresh interval, policy evaluation will return an effect of INDETERMINATE. External attribute stores are mutually exclusive to ACS in-built attribute store. Please refer to ACS API docs on Predix.io for more details
Auditing
With this release, ACS could be configured to audit its successful and unsuccessful API requests via external auditing service, e.g. Predix Audit Service.