This message was deleted.
# develocity
s
This message was deleted.
a
Hi @Aleksander Olszewski! Could you please create a support ticket, so that the relevant team can have a look into it? Thank you!
m
Hi @Aleksander Olszewski; there is a known bug I’m currently working on to fix that unfortunately leads to this problem. A workaround is to update your SAML IdP settings in Gradle Enterprise with a fresh metadata.xml file from Okta. If you use unattended configuration (aka gradle-enterprise.yaml) to set up your system, please make sure to update idpMetadata attribute in there as well.
a
Ok, thank you for update. I'll try to get new
metadata.xml
file (if I'm correct, there is no way to export it from Gradle Enterprise, right?) or upgrade to a version that is fixed (whatever comes first).
m
there is a way, but very complicated: 1. export your current configuration via Administration>Import/export>Export 2. Open the downloaded file and look for a field
idpMetadata
3. Base64 decode the value of
idpMetadata
and you get metadata.xml 4. Edit this file and set
entityID
attribute in root element to the correct value for your IdP (Okta) (use the Issuer element in a SAML response message taken from your browser network traffic, something like
http://www.okta.com/${org.externalKey}
) 5. Update your IdP metadata file in Administration>Access control>Identitity provider with the updated version Note: there will be no fix because your data are wrong; the bug was already fixed. There will be a chance to automatically correct the configuration data if there is a working SAML setup -> your 2022.4.7 instance with the next patch release, 2023.1.6. So waiting for the next patch release and updating your 2022.4.7 version should work. Let me know which route you will take.
a
Depending on workload, but currently it looks like I'll wait for the next patch release. But thank you for the workaround – I'll have it handy just in case šŸ‘