SAML logon not working on version 24: Illegal base64 character d
search cancel

SAML logon not working on version 24: Illegal base64 character d

book

Article ID: 398670

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine Automic SaaS CA Automic One Automation

Issue/Introduction

Users cannot logon anymore to Automic using SAML in case the IDP provides a Based64 Encoded signature with additional breaks (CRLF).

This was working fine on version 21.x and stopped working after upgrading to 24.4.0 HF2.

The error in the JWP log is the following:

20250513/123234.042 - 39 U00045325 Received SAML token as '<samlp:Response>'
20250513/123234.062 - 39 Unhandled Exception in thread MQWorker-X ID=YY
20250513/123234.062 - 39 U00045014 Exception 'java.lang.IllegalArgumentException: "Illegal base64 character d"' at 'java.util.Base64$Decoder.decode0():848'.

Environment

Automic Automation 24.x

Context: SAML authentitcation

Cause

DE170693

Resolution

Update to a fix version listed below or a newer version if available.

Fix version:
Component(s): Automation Engine
Automation.Engine 24.4.1 - Available

Additional Information

Public Description: A problem has been fixed where Base64 encoded SAML responses containing various whitespace characters were not correctly decoded.

Public Title: Unable to logon with SAML on v24 after upgrade from v21