Closed KTzerras closed 8 months ago
@KTzerras You have sensitive information here which needs to be redacted ASAP (Better would be create new issue). Can you share screenshot of the same, I went through the exact process a week or two ago ? I might be able to help.
@KTzerras
whereas we used the file che-cluster-patch.yaml with the following content:
Agree, the oAuthSecret field must be the following:
oAuthSecret: $(az ad app credential reset --id $(az ad app list --query "[?displayName=='$ECLIPSE_CHE_APPLICATION_DISPLAY_NAME'].id" --output tsv) --query "password" --output tsv)
Other than that, I successfully followed the doc and installed EclipseChe on Azure AKS. So, it hard to say what caused the problem above.
@maheshrajrp
ok, we have hidden the sensitive information.
Which screenshots do you mean exactly?
For the first I attach a screenshot of the file che-cluster-patch.yaml:
@tolusha After applying file che-cluster-patch.yaml being corrected according to your typo improvement it still does not work and delivers the same error.
After a discussion with Microsoft Azure Support the following root cause has been identified:
Since 15.11.2018 Azure AD stopped accepting previously used authentication codes for apps (c,f, https://learn.microsoft.com/en-us/entra/identity-platform/reference-breaking-changes#authorization-codes-can-no-longer-be-reused). Eclipse Che seems though that it still re-uses authentication codes to get tokens for multiple resources. And this leads to our error. According to this, an adaptation of Eclipse Che would be needed that shall a) use the authentication code to get a refresh token b) use that refresh token to acquire additional tokens for other resources
What do you think? Is this the case?
Hi @KTzerras , I think Eclipse Che follows this way. In any case, we were able to deploy so this flow is already working. My guess is probably some misconfiguration on your side.
"Access token validation failure. Invalid audience." This error seems to be with the authentication part of flow. Can you share a video or something that helps understand when this exception happens, more like the flow. It might help debug better.
Dear @maheshrajrp , so you mean you have managed to successfully deploy and use Eclipse Che on Azure Cloud? If yes, did you follow hereby the instructions from https://eclipse.dev/che/docs/stable/administration-guide/installing-che-on-microsoft-azure/ ? Or did you follow another approach? Thank you for your support, I really appreciate it ...
Yes, I followed the guide and was working for me.
Regarding the Linux Variable Issue, I work with Windows, so had to query and patch the values.yaml manually, so didn't encounter the variable issue. Aside from that, I believe to have followed only those mentioned step. We followed those steps and kept the deployment until we realized Azure Entra B2B Cost Pricing didn't justify the work we did hence had to try a different approach as mentioned here. Feel free to check that out if it matches your usecase.
What do you mean with "Linux Variable Issue"? (I also work with Windows)
I was pointing to this Typo Issue. https://github.com/eclipse-che/che-docs/pull/2695/commits/9991155f159140a96e6a10b9312bf341e4811a0b
@maheshrajrp Your use case does not really match our needs. We want to deploy and run Eclipse Che on the Azure Cloud and are ok with the Cost Pricing. I plan to repeat all steps from scratch and provide a precise description based on which we can then discuss possible solutions,.
I close it and shall open a new ticket later if needed.
@KTzerras you provided a Azure Active Directory Application Secret as part of your comment. I would highly suggest you to revoke or change it if its still active.
Yes I did within my desperate tries to install Eclipse Che on an Azure Cloud based on the idiotic official documentation. All these attampts were in vain, so we decided to abandon Eclipe Che from our company plans and take Eclipse Theia instead. So the cluster within which I provided the secret is history. With best regards Kostas
Describe the bug
We installed EclipseChe on the Azure Cloud according to the instructions under
https://eclipse.dev/che/docs/stable/administration-guide/installing-che-on-microsoft-azure/
Hereby we have used software-machines.online as DOMAIN_NAME (as instructed in section "Configuring DNS on Microsoft Azure").
According to section "Installing Che on Microsoft Azure Kubernetes Service" we deployed EclipseChe by the command
chectl server:deploy --platform=k8s --che-operator-cr-patch-yaml=che-cluster-patch.yaml --skip-oidc-provider-check --skip-cert-manager --domain=ide.software-machines.online
whereas we used the file che-cluster-patch.yaml with the following content:
All other instructions of page https://eclipse.dev/che/docs/stable/administration-guide/installing-che-on-microsoft-azure/ were executed 1:1.
Finally we navigated to the Che cluster instance via the command
chectl dashboard:open
and received 500 Internal Server Error in the Browser and in the log file we receive the following errors:
Can you please advise? Thank you in advance
Che version
7.81@latest
Steps to reproduce
Enter the URL ide.software-machines.online in a Browser. 500 Internal Server Error appears.
Expected behavior
The EclipseChe IDE starts without error.
Runtime
other (please specify in additional context)
Screenshots
No response
Installation method
chectl/latest
Environment
Windows
Eclipse Che Logs
Additional context
Azure