Change coming to the format of IP addresses containing IPV4 embedded in IPV6 addresses within token claims

Starting from July 8th, 2024, the format of IP addresses containing IPv4 embedded in IPv6 within token claims will be changing, affecting the 'ipaddr' claim in JWTs. The change impacts organizations that use custom applications dependent on the string format of this claim, requiring them to update their code. If there is no dependency on the string format, no action is needed. The Microsoft identity platform uses security tokens in the form of JSON Web Tokens (JWTs), containing claims that relay information about the token subject, including the IP address of the user authenticating. One of these claims, 'ipaddr,' will be affected by the change, regarding certain IPv6 addresses containing IPv4 addresses. These addresses will appear only as IPV6 addresses when serialized, without the embedded IPv4 addresses. The change will impact both access tokens and id tokens, as the 'ipaddr' claim is included in both token types. It's worth noting that despite the string format change, the IP addresses will remain the same.

If your organization doesn't depend on custom applications or on the string format of the 'ipaddr' claim from the access token or id token, there should be no impact, and no action is required.

The post Change coming to the format of IP addresses containing IPV4 embedded in IPV6 addresses within token claims originally appeared on M365 Admin.