Hi,
we are trying to connect via remote access and passthrough to an address that is reachable from the device.
We were able to complete the configuration in Remote Access, and the tab is now displayed as well.
When we open the corresponding tab, we get the message “no auth information found”.
There is no authentication implemented on the target system.
Does anyone know this issue or how to solve it?
DeviceManagement Version: 1023.97.4
Cloud-http-proxy Microservice Version: 2.12.1
Cloud HTTP proxy UI Version : 2.12.1
Cumulocity Tenant: eu-latest.cumulocity.com
Regards,
Valerian
Hi @v.reschke,
Can you check your browsers network tab and provide an extract of the requests performed to the Microservice endpoints?
It would also be interesting to see what headers are sent in the request that is actually failing here (please make sure to not include your full tokens when you provide these details).
It would also be interesting to know if your are using SSO or the default Cumulocity login and which auth strategy is configured for your tenant (Basic vs OAuth internal).
Regards,
Tristan
Hi @Tristan_Bastian ,
thanks for your reply. We have the following failed messages in the network tab.
we are not using SSO and the the auth strategy is “OAuth internal”.
Kind regards
Valerian
I found out that someone had changed the auth method to Basic. I have now reverted that change.
Now I’m getting the following error:
Does the Cookie header include an authorization cookie in the request sent to the service?
If so, can you provide a screenshot of the stored cookies (in Chrome: Application → Storage → Cookies) in your browsers developer tools?
in the request I’m getting now a 200 back:
but there are no logs in the microservice
yes there is an authorization part in the request Cookie header
here is the Screenshot of the Cookies:
So looks like everything is working as expected now with your 200 response code?
I’m still getting: “The site refused the connection” in the tab view.
If I click on “open in new tab” then I get this view:
Is there an explanation why this isn’t visible on the “Device-Tab”. Looks like something is blocking the iframe possibility.
Can you provide a bit more details what kind of page you are trying to connect to?
Can you also provide an extract of the network tab for all of the requests performed by this?
If you want you can also create an account for me on your tenant and I will take a closer look.
It seems like the webserver you are trying to access is blocking iframes:
Refused to display 'https://<tenantDomain>/' in a frame because it set 'X-Frame-Options' to 'deny'.
Therefore the page only loads the loading screen when you access it in a new tab.
The page then stops at the loading indicator since the application you are trying to access is not optimized for being served behind a reverse proxy.. All the requests for further static assets (JavaScript and CSS) of the page fail since they are loaded from the wrong path:
The application requests these files from https://<tenantDomain>/js_lib/dust-full-2.1.0.js instead of https://<tenantDomain>/service/cloud-http-proxy/7756704292/3/js_lib/dust-full-2.1.0.js.
This happens since the applications specifies an absolute path instead of an relative path in the initially loaded html:
<script src="/js_lib/dust-full-2.1.0.js" defer="defer" type="text/javascript"></script>.
There is not much we can do about this.. you would probably have to get in touch with the producer of the application to get this adjusted.
thanks for taking the time to analyze the issue. We will review the target site and also check with the manufacturer to see if this can be adjusted. Many thanks for your support and for providing the necessary information.
we’ve made some changes on the target server, but unfortunately we still can’t establish a connection.
When we open the tab for the remote target, we’re getting a login prompt.
We tried both our Cumulocity credentials and the credentials for the target server itself, but neither worked.
In the configuration view we can see that an Authorization header is being sent.
Does anyone know which credentials are actually expected for this header in this context?
Are these supposed to be:
- Cumulocity tenant/user credentials,
- local server (OS/application) credentials, or
- some separate set of credentials (e.g. a technical user, API user, etc.)?
Any clarification or example configuration would be very helpful.
The headers you configure are the headers that would be sent to the application.
As you didn’t provide any details on what kind of application you are trying to access, we can’t really help with what kind of headers might be required here..
These can be any credentials/API keys that you would usually use with the application you are trying to access..
Thanks for your reply. We want to access the configuration interface of another device.
The header that is being sent should works for this config page.
What we don’t understand is: what is this login pop-up for?
