What's new in oxd 4.2#
oxd 4.2 includes architectural changes as well as different bug fixes and improvements:
- Support RDBMS, LDAP and Couchbase for oxd storage
- Upgraded Dropwizard to 2.0.0 version
- Added feature to automatically synchronize with the client data from OP
- Profile and monitor the oxd end-points using OpenTracing
- Install oxd as a service on Windows OS using exe file
- Added features to support HA of oxd
- Included validations and improvements in oxd apis (Example: To generate
client-jwksand request_uri etc.)
oxd 4.0 includes architectural changes as well as different bug fixes and improvements:
- Introduced Swagger 2.0 to oxd (we are planning to move to 3.0 when swagger codegen is ready)
- Socket transport is removed from oxd-server
- https is the main transport layer for oxd-server
- oxd-https-extension module is completely removed
- All configuration is now in a single yaml file. See a sample oxd-server.yml
- New tests set-up and tear-down based on Dropwizard
- Upgraded dropwizard to latest stable 1.3.1 version
- Changed oxd commands runner to avoid additional serialization/deserialization which improves performance.
oxd 3.1.4 includes bug fixes, updated UMA scopes, and to improve usability and administration.
Now Open Source#
In oxd 3.1.4, we removed license validation and made the code open source under the Apache2 license!
Updated UMA scopes#
In coordination with enhancements to oxAuth 3.1.4, we've updated and renamed UMA scopes within oxd.
Build without Git#
We've added the ability to build oxd without Git, allowing the package to be downloaded as a zip file.
Improved client validation and logging#
To enhance oxd's usability, we've improved
access_token validation and adjusted our logging parameters.
oxd 3.1.3 includes improvements to the oxd-https-extension, new features to better support Gluu Gateway, and bug fixes to improve usability and administration.
Tighter Gluu Gateway integration#
oxd 3.1.3 includes improvements to existing functionality to work better with Gluu Gateway, such as the ability to update existing UMA resources in the Gluu Server.
Better https extension#
We've expanded our initialization script for the oxd HTTPS extension to increase performance and make configuration easier.
Up to 10 OAuth 2.0 clients free, forever!#
We wanted to build the oxd ecosystem, so now all accounts include up to 10 OAuth 2.0 clients free forever. All clients in excess of 10 will still be charged $0.33 per day.
Review the oxd 3.1.3 release notes for a full list of fixes and new features in oxd 3.1.3.
oxd 3.1.2 includes bug fixes, easier administration, and additional security features.
Better OAuth 2.0 support#
oxd 3.1.2 features more comprehensive support for OAuth 2.0, including a new access token introspection command, an UMA RPT introspection command, and support for
or logical operations.
oxd 3.1.2 includes a new command to remove a client from oxd. This is helpful to keep the server organzied and uncluttered.
Review the oxd 3.1.2 release notes for a full list of fixes and new features in oxd 3.1.2.
We've made significant updates to oxd 3.1.1 to improve performance and functionality.
oxd 2.4.4 and 3.0.1 were billed USD $0.33 per server per day. oxd 3.1.1 is billed USD $0.33 per application per day
Existing and/or new installations of oxd 2.4.4 and oxd 3.0.1 will continue to be billed per server per day
New or upgraded oxd 3.1.1 deployments will be subject to the new per application billing model
Learn more about pricing & billing.
oxd 3.1.1 includes a new component called the
oxd-https-extension. The extension is included out-of-the-box in the oxd Linux packages--it simply needs to be started. With the
oxd-https-extension, applications can make RESTful calls to your oxd server over the web.
Gluu Server and oxd 3.1.1 are the first commercially supported IAM server and clients to implement the UMA 2.0 Grant for OAuth 2.0 Authorization and Federated Authorization specifications. UMA 2.0 now aligns completely with OAuth 2.0. It also re-defines the claims gathering flow, enabling developers to implement multi-step consent, user-interactions, and stepped-up authentication flows.
oxd 3.1.1 now supports in-memory or redis caching of data to improve throughput for OpenID Connect and UMA clients.
oxd 3.1.1 includes an auto-migration process to transfer your existing oxd JSON files to your new oxd 3.1.1 server(s).
Please review the following legacy compatibility considerations while evaluating your upgrade path to oxd 3.1.2:
UMA 2.0: Supported in oxd 3.1.2 and Gluu Server 3.1.1
UMA 1.0.1: Not supported in oxd 3.1.1or Gluu Server 3.1.1
OpenID Connect: Supported in all versions of oxd and Gluu Server
Pricing: If you upgrade existing oxd installations to oxd 3.1.1, the new per application billing model described above will take effect. This could have an impact on your monthly bill
Review the oxd 3.1.1 release notes for a full list of fixes and new features in oxd 3.1.1.