Open Tarzac opened 2 months ago
is your IDP accessible publicly ?
This issue is purely functional from what I can see and is not a bug with the provider. The error you have is from the platform's API
However, the same request works via the API :
Request:
POST https://anypoint.mulesoft.com/accounts/api/organizations/xxx/identityProviders
{
"type": {
"description": "OpenID Connect",
"name": "openid"
},
"oidc_provider": {
"client": {
"credentials": {
"id": "xxxxx-xxxx-xxxx",
"secret": "xxxx-xxxx-xxx-xxx-xxxxxxxxx"
}
},
"urls": {
"authorize": "http://idp.example.com/auth/realms/master/protocol/openid-connect/auth",
"token": "http://idp.example.com/auth/realms/master/protocol/openid-connect/token",
"userinfo": "http://idp.example.com/auth/realms/master/protocol/openid-connect/userinfo"
}
},
"allow_untrusted_certificates": true,
"login_disabled": false,
"name": "openid connect provider 2"
}
Response:
{
"provider_id": "xxxx",
"org_id": "xx",
"name": "openid connect provider 2",
"type": {
"description": "OpenID Connect",
"name": "openid"
},
"oidc_provider": {
"urls": {
"token": "http://idp.example.com/auth/realms/master/protocol/openid-connect/token",
"redirect": "https://anypoint.mulesoft.com/accounts/login/xxxx/providers/xxxx",
"userinfo": "http://idp.example.com/auth/realms/master/protocol/openid-connect/userinfo",
"authorize": "http://idp.example.com/auth/realms/master/protocol/openid-connect/auth"
},
"client": {
"credentials": {
"id": "xxxxx-xxxx-xxxx"
}
}
},
"service_provider": {
"urls": {
"sign_on": "http://idp.example.com/auth/realms/master/protocol/openid-connect/auth?response_type=code&scope=openid%20profile%20email&client_id=xxxxx-xxxx-xxxx&redirect_uri=https%3A%2F%2Fanypoint.mulesoft.com%2Faccounts%2Flogin%2Fxxxxx%2Fproviders%xxxxx%2Fredirect"
}
},
"allow_untrusted_certificates": true,
"arc_namespace": null
}
There is a bug when creating an IPD with an "Identity Client Registration" of type "Manual Registration".
Source :
Result :