Browser Access in version 920130 redirects wrong. Any suggestions?

[ChairatJ]

When working on Browser Access in Business One, it redirects from the dispatcher URL to go to the BSO login page of SLD. This redirect doesn't work. It goes to https://IPaddress:40000/saml2/idp/sso (HANA installation) or https://IPaddress:30010/saml2/idp/sso (SQL installation)

and shows a blank page.

It looks like it is redirecting to a single sign on but I don't use that. Further, this is the case on SQL (on microsoft Azure) and Hana (AWS). Both are on version 920130. In the first 9.2 version all is working.

I have done various things in ControlCenter and the SLD-config.xml file and after that restarted the services.

The content of the SLD-config.xml is:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<ServiceLandscapeDirectory>

    <location>https://induit:30010</location>

    <loginCredential>

        <name>service</name>

        <password>846924b840485e0b4b308c0e6073cd1deb43b90d346d10eac521e137d977c5520x110x33</password>

    </loginCredential>

    <componentID>1</componentID>

    <componentType>B1WebServers</componentType>

</ServiceLandscapeDirectory>

and attached is a screen shot of the Control Center and the page after redirecting from the dispatcher page.

Any suggestions?

Thanks,

Peter

[former_member198649]

Dear Peter,

Is this accessable from inside your network properly or the same thing happens inside too??

[ChairatJ]

Internally on the internal IP it is working. Then it is redirected to:

https://172.31.8.119:40000/ControlCenter/sbo.html?saml2TokenRef=2c78d5d2-092d-477e-8c42-ba65dcac7aff

[ChairatJ]

from external it goes to:

https://54.198.92.175:40000/saml2/idp/sso

[ChairatJ]

I also had earlier the SLD-config.xml file edited with in the location url ControlCenter. Then if I remember correctly it redirected to:

https://54.198.92.175:40000/ControlCenter/saml2/idp/sso

[former_member198649]

Dear Peter,

I just setup External Browser Setup yesterday. My problem is little different from you. But I found that the Server Name in SLD-cofig.xml is the problem. Make sure when you install browser service you gave the dispatcher address with the IP (I use Internal IP and which was redirected with extenal IP) not with the Server Name. In your SLD-Config.xml file the location is  <location>https://induit:30010</location>

which is indicate to server name not the IP.

For reference I post here a Thread which was helped me.

[ChairatJ]

Actually, the current SLD-config is as follows (local IP address) the one earlier was a working version on older SAP Business One):

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<ServiceLandscapeDirectory>

    <location>https://172.31.8.119:40000</location>

    <loginCredential>

        <name>service</name>

        <password>f8425f379524e7d91a577e181ac6ff2b7d541a3e6e0660c64b0820d22676c86f0x110x33</password>

    </loginCredential>

    <componentID>1</componentID>

    <componentType>B1WebServers</componentType>

</ServiceLandscapeDirectory>

[ChairatJ]

Hi Tariq,

Will give it a try.

Peter

[ChairatJ]

Just re-installed browser access but still the same issue. It redirects to the sso url and shows an empty page.

[former_member198649]

Peter,

what is the value of new SLD-config.xml in location?

also can I check the dispatcher link with my side?

[ChairatJ]

Actually, the SLD-config after re-install had the server name, not IP address. But two points on this.

1. Another installation I have on an older version of 9.2 also has the server name and that works.

2. Just for your information, all services are running on one machine (SQL, SLD, license, Browser access, etc..) That's why it works on the older installation.

Any ideas?

Thanks,

Peter

[former_member198649]

Dear Peter,

I check your external location but it is not responding.

This site can’t be reached

(YOUR IP) took too long to respond.

Try:

• Checking the connection
• Checking the proxy and the firewall

ERR_CONNECTION_TIMED_OUT

[patrice_vigier]

Hello Peter

Did you find a solution ? I have the same problem with SAP Hana 9.2 PL03

Thank you