apigee-sso installation using local metadata xml file
Hi All, We are trying to install apigee-sso module on Apigee on premise v4.19.01 using local metadata xml file provided by our IDP. We know that in v4.19.01 there's a known issue which gives error while installing sso using local metadata : When installing apigee-sso and using a metadata.xml file instead of a URL, if the metadata.xml file does not include a new line (CRLF) at the end of the file, the metadata.xml file is not read entirely.
Apigee has provided a workaround for this in their release note: https://docs.apigee.com/release/notes/41901-edge-private-cloud-release-notes#known-issues
To work around this issue, you can do one of the following: Add a CRLF to the end of the metadata.xml file.
We tried to use this workaround in our case by adding a new line at the end of the metadata xml but it is still giving the same error. Has anyone tried this method to install apigee-sso? If yes, can you please provide the correct method to use a CRLF at the end of the file.
> We tried to use this workaround in our case by adding a new line at the end of the metadata xml
Did you do this on Windows or Linux? Windows and Linux have different definitions of what a "new line" means. Apigee SSO needs the Linux variant (CRLF).
@Christian King
We tried this workaround in Linux. We added a new line at the end of metadata.xml but it didn't work. Is there any specific format we have to use for CRLF in Linux?
So long as you used a standard Linux text editor, it will use CRLF as a newline. You can also use dos2unix on the file to confirm the newline is in the correct format.
If it still doesn't work after that, I suspect the lack of trailing CRLF isn't your issue and it may be something more complex.
