Describe the bug

• Jenkins: 2.516.1
• plugin SAML Single Sign On(SSO): 2.4.7
• logto: v1.28.0

SAML SSO plugin config

SAML metadata validate success, On jenkins login page login with IDP, will direct to MY_LOGTO_HOST/sign-in, create user and login, I catured maybe incorrect directs https://MY_LOGTO_HOST/api/saml-applications/20j77la181ug6ti0new1k/callback?code=LizgYc3CA0wAlalhFRixI849d5Ya7-rXDYHp4V50731&state=ighr4zu6ns29b690b6phm3t096cjv51k&iss=https%3A%2F%2FMY_LOGTO_HOST%2Foidc
but AUTHENTICATION applications 20j77la181ug6ti0new1k is a SAML App

if possible, please provide more examples show how to integrate much more popular devops tools example?
alike:

• jenkins
• gitlab-ce
• artifactory
• kubesphere

Expected behavior

logto SAML should pretty works with jenkins SAML plugins, and correct bring final login user to jenkins.

How to reproduce?

create self-host logto instance, In logto admin panel, create a AUTHENTICATION SAML application

create self-host jenkins instance
install plugin SAML Single Sign On(SSO): 2.4.7
in jenkins Security, change Security Realm to miniOrange SAML 2.0 and save goto /manage/MoPluginConfigView/
on section Enter metadata url: enter logto SAML application MY_LOGTO_HOST/api/saml-applications/20j77la181ug6ti0new1k/metadata click Validate metadata Url and click page bottom SAVE

logout current jenkins user, On jenkins login page login with IDP, will direct to MY_LOGTO_HOST/sign-in, create user and login, not logind, just show page /securityRealm/moSamlAuth

Environment

Self-hosted (Docker image)

Screenshots

No response