You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info
On Tuesday, October 17, 2017, we began releasing a new version of Apigee Edge for Public Cloud.
New features and updates
Following are the new features and updates in this release.
Self-service virtual hosts for Edge Cloud (Beta for Edge paid plans)
This release of Edge for the Cloud includes the Beta release of self-service virtual hosts. Self-service virtual hosts let Edge Cloud customers on paid accounts create, modify, and delete virtual hosts. Previously, these actions had to be performed by Apigee Support.
Before you begin to use this feature, ensure that you have reviewed the FAQ and all Beta documentation.
The documentation for this Beta release includes:
|Name validations on new entities
When you create new entities, Apigee validates the names to enforce naming rules. Entities being validated on creation or update are: API proxies, policies (and policy names in API proxy definitions), virtual hosts, roles, caches, target servers, data masks for debugging, keystores and truststores, and resource files in API proxies. See Naming and input error advisories for naming restrictions on these entities.
The following bugs are fixed in this release. This list is primarily for users checking to see if their support tickets have been fixed. It's not designed to provide detailed information for all users.
|MGMT to send org and env header to blobstore
|Support enabled for PKS format certs
|Optimal default consistency level value for identity-zone
|Resolve timeout issue for retrieving OAuth2 tokens by an appId
|Ability to disable Basic Authentication Scheme in SecurityProfile
|Need a CWC token to set JVM_OPTIONS on all Java components
|Auto URL-encode special characters in permission paths for custom roles
|Upgrade CPS version to 1.1.14
|Fixed OAuth service NPE issue
|Allow time to drain connections before killing unhealthy service
|Basic authorization for BlobstoreService
|Sense Action should continue to function if Zookeeper is down
|Reuse refresh token attribute support enabled for OAuth policies
|Rolling window quota counter not being calculated accurately
|Flow hook not deploying consistently, ZooKeeper check not working
|The MP Sense Task ended without notice
|Analytics doesn't work for monetization-enabled message processors if the org region is different from the axgroup region
|Compute error rates per target per error code
|RepositoryServiceImpl.loadAsString() doesn't use charset
|High memory usage on org MPs
|Capture TLS version in Nginx access_log for every request
|Current version of Nginx doesn't support variable combination required for X-Forwarded-For header
|Tokens are not recorded as hashed after turning on hashing
|OAuth token not holding the set attribute in a subsequent call
|messaging.adaptors.http.flow.ServiceUnavailable error with Concurrent Rate Limit policy
|Add MP pod name in the header to router X-Apigee-Pod
|Cache changes are not getting replicated to a specific message processor
|Message Logging policy syslog timestamp format is not correct
|QuotaService for non-CPS flow should clean up buckets asynchronously and not in Apigee-Main thread
|print statement fails with NPE
|Only MPs should register in consul KV path
|High request processing latency on MPs
|Unhandled exceptions does not cause Node.js/Trireme process to exit
|mongodb-core in Trireme produces different crypto results than native Node.js
|Node security: http.get with numeric authorization options creates uninitialized buffers
|Trireme returns Invalid verify algorithm sha256 error
|Node apps experiencing x_apigee_fault_code: "scripts.node.runtime.ScriptExecutionError"