What's New
IBM will no longer host IBM Security Verify containers on Docker Hub after December 31st, 2022
All containers should be sourced from the IBM Cloud Container Registry, see Software Downloads > Containers for more information.
This may be a breaking change to any automated deployment processes.
Requesting new features
Ideas for new features can be submitted using the IBM Application Gateway Ideas Community.
v23.04
Critical Change - Container Availability
- IBM Application Gateway and all supporting containers are now only available from IBM Cloud Container Registry. (see: Software Downloads > Containers)
Rate Limiting
- Additional Rate limiting headers can now be added to responses, indicating which policy is being applied, how many more requests can be made and the time the policy will reset. (see: server/rate_limiting)
Username/Password Single Sign-on
- When using forms-based single sign-on, an additional pattern can be specified to detect if the login resource contains the login form. (see: forms_login/login_resources[]/form_response_pattern)
General
- Bug Fixes, Security Updates and behind the scenes improvements.
v22.07
Critical Change - Content Security Policy
- The application gateway will now apply a strong Content Security Policy by default for server generated responses. (see: Tasks/Custom Pages/Content Security Policy)
Public Assets
- The application gateway can now serve a set of public assets, which are resources available to all clients regardless of whether or not they are authenticated.
- The default set of error and management pages has been updated to conform with the new stricter Content Security Policy. The embedded JavaScript and CSS has now been moved to the public assets area. (see: Tasks/Custom Pages/Public Assets)
Language Control
- It is now possible to control the languages which the application gateway will use when populating error and message macros. (see: Tasks/Custom Pages/Controlling the Language of Translated Messages)
HTTP Transformations with Lua
- HTTP Transformations can now be performed using the Lua scripting language. (see: Tasks/HTTP Transformations)
Kubernetes Operator
- The Kubernetes Operator has been published to the RedHat operator catalog
- Sidecar support is now configured automatically as a part of the Kubernetes Operator deployment
v21.12
Re-authentication
- Authorization policies can now indicate that a client must re-authenticate before accessing a resource. (see: Tasks/Re-Authentication)
Rate Limiting
- Rate limiting data can now be distributed across multiple IAG instances using a Redis database. (See Sharing rate limiting data across instances, server/rate_limiting and services/redis)
General
- Bug Fixes, Security Updates and behind the scenes improvements.
v21.09
General
- Bug Fixes, Security Updates and behind the scenes improvements.
v21.06
Authentication Flow Redirects
- IAG can now redirect clients to a configured URL when authentication is completed. (See Controlling Redirects, and auth_complete_redirect)
Other
- Additional Bug Fixes, Security Updates and behind the scenes improvements.
v21.04
PROXY Protocol Support
- IAG now supports the PROXY protocol for identifying clients. (See PROXY Protocol, server/protocols, server/client_ip_rules)
OAuth Introspection
- IAG can now include additional HTTP headers when making requests to OAuth introspection endpoints. (see oauth)
Resource Severs
- Each server in a resource server can now be assigned a priority group, which can be used to control which server IAG will direct traffic to. (See Multi-server Applications and resource_servers[]/servers)
- The UUID of each each server in a resource server can now be configured, which allows stateful applications to span multiple instances. (see Stateful Applications and resource_servers[]/servers)
Kubernetes
- IAG can now directly reference data from a Kubernetes ConfigMap by name and field in the configuration YAML (see: "Special Types Available in Kubernetes" in Concepts/Configuration)
v21.02
Identity
- IAG can now direct unauthenticated clients to a specific URL to perform authentication. (See auth_challenge_redirect)
- Applications running on protected resource servers can now authenticate clients using the External Authentication Interface. (See External Authentication)
Policy
- An authorization policy can now redirect clients to a specific URL when denying access. (See obligation/redirect_url)
Configuration YAML User Interface
- A new browser based application which can be used to author and visualise the IAG configuration YAML has been made available at the following URL: ibm.biz/ibm-app-gateway-yaml.
v20.12
Session Sharing Between Containers
- Session state can now be stored in an external Redis database and shared between multiple instances of IAG. (see Sharing Sessions Between Containers)
Kerberos Constrained Delegation Single Sign-On
- IAG can now perform single sign-on to Kerberos protected resource servers using Constrained Delegation. (see Passing Identity Information to Applications)
OAuth Introspection
- IAG can now perform OAuth introspection to authenticate clients. (see Protecting Applications with IBM Security Verify and Protecting Applications with IBM Security Verify Access)
v20.09
Kubernetes Operator
- A new Kubernetes operator can be used to configure and manage IAG instances. (see Deployment/Kubernetes/Overview)
- The Kubernetes operator is available from OperatorHub.io. (See Deployment/Kubernetes/OperatorHub)
- The Kubernetes operator can produce combined configuration from multiple sources, including literal definitions, config maps and web-based sources. (See Deployment/Kubernetes/Operator)
- The Kubernetes operator can be used for sidecar injection when deploying applications in Kubernetes. (See Deployment/Kubernetes/Sidecar)
- The Kubernetes operator can perform dynamic OIDC client registration to register new OIDC clients for IAG instances with the identity provider. (See Deployment/Kubernetes/OIDC Dynamic Client)
Username/Password Single Sign-on
- IAG can now retrieve credentials for use in single sign-on from an external credential service. (see Using a Credential service for single sign-on)
- Externally provided credentials can be used to perform basic authentication to protected applications. (see identity_headers#basic_auth)
- Externally provided credentials can be used to perform forms-based single sign-on to protected applications. (see forms_login)
LTPA Single Sign-on
- IAG can now generate LTPA token for single sign-on to protected applications. (see identity_headers/ltpa)
Demo
- A new "Hello World" topic which demonstrates the various IAG deployment models has been added to the Developer Portal (see Hello World in the sidebar)
- A new demonstration resource server application has been created. This application can be used when exploring IAG deployment models or experimenting with configuration (see References/Demo Resource Server)
Preview Capability: OAuth Introspection
- IAG can now perform OAuth introspection to authenticate clients. (see Current Preview Features)
Note: This is a preview capability and may be changed in a future release.
v20.07
Authentication
- Authentication requirements can now be enforced as part of an authorization policy (see: Tasks/Authentication Requirements)
Configuration
- IAG can now read obfuscated and encrypted entries from the configuration YAML (see: "Special Types" in Concepts/Configuration)
- Certificate related entries can now be specified as an array of certificate and key entries and do not need to be concatenated into a single string (see: Tasks/Managing Certificates)
Kubernetes
- IAG can now directly reference data from Kubernetes Secrets by name and field in the configuration YAML (see: "Special Types Available in Kubernetes" in Concepts/Configuration)
v20.04
Identity
- Credentials from an IBM Security Verify Access or IBM Security Access Manager 9.0.7.0+ identity provider can be consumed, where IBM Application Gateway (IAG) acts as OpenID Connect (OIDC) Relying Party (see: Protecting Web Applications with IBM Security Verify Access);
- The 'identity/ci_oidc' YAML configuration node is no longer the preferred way to configure IBM Security Verify as the Identity Provider. The new 'identity/oidc' YAML configuration node should be used instead (see: OIDC).
Server
- IAG can now be configured to listen on port 8080 for HTTP traffic (see: Server/Protocols)
v20.01
Application Protection
- Signed JSON Web tokens (JWT) can now be generated and sent to resource servers (see: Passing Identity Information to Applications);
- The content injection capability now supports a partial line match (see Inserting Content into Responses).
Logging
- Statistics information can now be sent to a remote statsd server for monitoring purposes (see: Enabling Statistics Gathering);
v19.12 (Initial Release)
Identity
- Credentials from an IBM Security Verify tenant can be consumed, where IBM Application Gateway (IAG) acts as OpenID Connect (OIDC) Relying Party (see: Protecting Web Applications with IBM Security Verify);
Application Protection
- An application can be defined and identified using either a path or host header (see: Protecting an Application);
- An attribute/claims based authorization policy can be defined to control access to resources (see: Defining the Authorization Policy);
- Access to resources can be rate limited (see: Rate Limiting Requests);
- HTTP requests or responses can be modified using XSLT defined rules (see: Transforming Requests and Responses);
- Cross-Origin Resource Sharing (CORS) policies can be handled on behalf of the application (see: Defining the Cross-Origin Resource Sharing Policy);
Logging
- Tracing, statistics gathering and performance metrics can be used to help diagnose issues in the environment.
Updated about 2 months ago