Unable to connect to Datasphere using the CLI

[Thibault_dockx]

Since the latest release of Datasphere we need to provide a redirect URI during OAuth Client creation. This causes issues since we cannot provide the code it gives, back to the CLI. This way we are unable to connect to Datasphere using command lines. 

Any tips/ ideas or workarounds for this issue? Happy to discuss.

Kind regards,

Thibault

[irodin10]

If anyone still has a problem with the localhost solution showing "This site can’t provide a secure connection", then take a look at this https://apple.stackexchange.com/questions/266573/fix-localhost-cant-provide-a-secure-connection - that fixed it for me (on mac with chrome browser).

[XaviPolo]

In my case, even though the Datasphere configuration specifies http://localhost:8080, it always opens https://localhost (with the ‘s’ and on port 443). I have to manually edit the browser URL to the correct one, press enter, and then it works.

Regards,

[TuncayKaraca]

Hi Thibault,

It's interesting to see there is only one change regarding OAuth Client in the latest version 2024.8

But it's not directly anything about OAuth Client's redirect URI! It's just about token and refresh token lifetimes. 

There must be an issue related to this change. You can reach SAP support and submit an incident. 

Regards,
Tuncay

[kostertim]

Think if you set it up as API Access it should still work?

[TuncayKaraca]

@Thibault_dockx  - @kostertim has provided the solution here.

"I have updated the scripts to get it working again. Make sure that you use this for the Redirect URI: http://localhost:8080"

Regards,
Tuncay

[irodin10]

Haven't managed to get it running either since the changes to the oAuth Client in Datasphere. Neither with API access nor with Interactive. Curious if anyone finds a solution.

[kostertim]

You need to set-up the Redirect URI as: http://localhost:8080

Just use the "normal" Interactive Usage oAuth method. 

[TuncayKaraca]

Oh I see there is answer here too! Thanks @kostertim