Troubleshooting
S-Pankki: "SSO: Tunnistusagentti epäonnistui"
Applies to
- SSO Server 6.8
- TUPAS 2.3c, S-Pankki
Symptoms
- Use case: testing authentication first time in production environment
- TUPAS authentication with S-Pankki failed
- SSO Server error: "tunnistusagentti epäonnistui" displayed in browser
Figure 1. SSO Web agent failed with S-Pankki TUPAS method "Tunnistusagentti epäonnistui" |
Causes and resolutions
Service provider (MAC key) was delivered from S-Pankki as hexadecimal. This needed to be converted to string in Ubisecure SSO Server Management, mackey1 field (please see Figure 2 on page Installing the TUPAS Authentication Method).Â
Nordea: "Palvelusopimusta ei löydy (V2322A1M)" and "Paluulinkki on virheellinen. (V2363A13)"
Applies to
- SSO Server 6.8
- TUPAS 2.3c, Nordea
Symptoms
- Use case: testing authentication first time in production environment
- TUPAS authentication with Nordea failed
- Nordea: "Palvelusopimusta ei löydy" displayed in browser
- Nordea: " Paluulinkki on virheellinen. (V2363A13)" displayed in browser
Figure 2. SSO Web agent failed with Nordea TUPAS method "Palvelusopimusta ei löydy" |
Causes and resolutions
- Service provider (A01Y_RCVID / Customer code) was delivered from Nordea with additional hyphen. Please remove it in Ubisecure SSO Server Management, rcvid field (please see Figure 2 on page Installing the TUPAS authentication method).
- Return address (A01Y_RETLINK) should be defined in Nordea TUPAS service as
https://[UBISECURE SSO SERVER ADDRESS]/uas/return/nordea.1/Â
where nordea.1Â is authentication method name in Ubisecure SSO Server.Nordea service contract needs to point to [UBISECURE SSO SERVER ADDRESS], otherwise retlink cant be used.
Handelsbanken: Virheellinen sanoma. Virhe 03.
Applies to
- SSO Server 6.8
- TUPAS 2.3c, Handelsbanken
- Use case: testing authentication first time in production environment
Symptoms
- Use case: testing authentication first time in production environment
- TUPAS authentication with Handelsbanken failed
- Handelsbanken: " Virheellinen sanoma. Virhe 03" displayed in browser
Cause and resolution
One possible cause and resolution might be, that service provider (A01Y_RCVID / Customer code) delivered from Handelsbanken lacked three zeros (000) from the end. If that was the cause, please add three zeroes to Handelsbanken TUPAS authentication method in Ubisecure SSO Server Management, rcvid field (please see Figure 2 on page Installing the TUPAS authentication method).
If you continue to have problems, please contact Handesbanken support.