gtejo1 Absent Member.
Absent Member.
1178 views

UA OSP - Invalid host header name or request url domain name

Hello everyone, after succesfully updated the client development enviroment to the version 4.7.0, y proceeded to do the upgrade to the patch 4.7.2 (once i had tried it in my enviroment). Now after upgraded all the modules, including the UA, when i try access the UA with the very well know URL adress and then this error shows up:



So looking in the logs... tomcat shows me no error; but the osp log show me this:



This is the configupdate actual configuration:





I already checked the osp keystore and the tomcat keystore and both have the same CA certificate. Can anyone give me a hand? I already considered do a clean install, but i prefer to avoid this method.
Labels (1)
0 Likes
20 Replies
gtejo1 Absent Member.
Absent Member.

Re: UA OSP - Invalid host header name or request url domain

Sorry, this is the osp log:
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: UA OSP - Invalid host header name or request url domain name

gtejo <gtejo@no-mx.forums.microfocus.com> wrote:
>

Sorry, this is the osp log:
[image: https://i.imgur.com/ertQ1rB.png]


--
gtejo
------------------------------------------------------------------------
gtejo's Profile: https://forums.novell.com/member.php?userid=116263
View this thread: https://forums.novell.com/showthread.php?t=512039

>


Hi.

I dont think this is your error. Look for SEVERE text in the osp log file.

--
Best regards
Marcus
0 Likes
gtejo1 Absent Member.
Absent Member.

Re: UA OSP - Invalid host header name or request url domain

The last one here, is the title of the post:

0 Likes
gtejo1 Absent Member.
Absent Member.

Re: UA OSP - Invalid host header name or request url domain

Anyone has any clue about this error?
0 Likes
gtejo1 Absent Member.
Absent Member.

Re: UA OSP - Invalid host header name or request url domain

Well, i was stucked so i restored the snapshot point i started the update again. Doing exactly the same steps (and the UA working fine in version 4.7.0) i reach to the same error. I Tried to update the OSP certificate in the Java cacerts of the UA, the Java cacerts of eDirectory and in the tomcat keystore. The error still persist.
0 Likes
Knowledge Partner
Knowledge Partner

Re: UA OSP - Invalid host header name or request url domain name

On 4/29/2019 1:24 PM, gtejo wrote:
>
> Well, i was stucked so i restored the snapshot point i started the
> update again. Doing exactly the same steps (and the UA working fine in
> version 4.7.0) i reach to the same error. I Tried to update the OSP
> certificate in the Java cacerts of the UA, the Java cacerts of
> eDirectory and in the tomcat keystore. The error still persist.


And tomcat public key into the osp and cacerts keystores.


0 Likes
gtejo1 Absent Member.
Absent Member.

Re: UA OSP - Invalid host header name or request url domain

They already have those, since before the upgrade the ua was working, they have the same certificates. Now i modified the setenv of the tomcat to set the logging of the OSP in ALL. This is what i see, the error is clear but even if i change the URL in the configupdate i get the same error. Any clue?
0 Likes
Knowledge Partner
Knowledge Partner

Re: UA OSP - Invalid host header name or request url domain name

On 4/29/2019 5:16 PM, gtejo wrote:
>
> They already have those, since before the upgrade the ua was working,
> they have the same certificates. Now i modified the setenv of the tomcat
> to set the logging of the OSP in ALL. This is what i see, the error is
> clear but even if i change the URL in the configupdate i get the same
> error. Any clue?
> [image: https://i.imgur.com/zftOeWQ.png]


Why would you not paste that as text, instead posting as a screen shot?
You reduce the amount of help you will get by pasting as screen shot.

Does your /etc/hosts define the full DNS name of the server for its IP?

0 Likes
gtejo1 Absent Member.
Absent Member.

Re: UA OSP - Invalid host header name or request url domain

geoffc;2499018 wrote:
On 4/29/2019 5:16 PM, gtejo wrote:
>
> They already have those, since before the upgrade the ua was working,
> they have the same certificates. Now i modified the setenv of the tomcat
> to set the logging of the OSP in ALL. This is what i see, the error is
> clear but even if i change the URL in the configupdate i get the same
> error. Any clue?
> [image: https://i.imgur.com/zftOeWQ.png]


Why would you not paste that as text, instead posting as a screen shot?
You reduce the amount of help you will get by pasting as screen shot.

Does your /etc/hosts define the full DNS name of the server for its IP?


Thanks for the recommendation, next time I'll use the text. Yes it does, the host has the IP of the server and the DNS that IDM uses. What bothers me is that after doing the upgrade, there are the same configurations with which the UA worked before doing it.
0 Likes
Knowledge Partner
Knowledge Partner

Re: UA OSP - Invalid host header name or request url domain name

On 4/30/2019 10:04 AM, gtejo wrote:
>
> geoffc;2499018 Wrote:
>> On 4/29/2019 5:16 PM, gtejo wrote:
>>>
>>> They already have those, since before the upgrade the ua was working,
>>> they have the same certificates. Now i modified the setenv of the

>> tomcat
>>> to set the logging of the OSP in ALL. This is what i see, the error

>> is
>>> clear but even if i change the URL in the configupdate i get the same
>>> error. Any clue?
>>> [image: https://i.imgur.com/zftOeWQ.png]

>>
>> Why would you not paste that as text, instead posting as a screen shot?
>> You reduce the amount of help you will get by pasting as screen shot.
>>
>> Does your /etc/hosts define the full DNS name of the server for its IP?

>
> Thanks for the recommendation, next time I'll use the text. Yes it does,
> the host has the IP of the server and the DNS that IDM uses.


More sepcificaly, I was asking if the entry looks something like this:

10.1.1.1 serverName servername.acme.com

Not just
10.1.1.1 serverName


0 Likes
gtejo1 Absent Member.
Absent Member.

Re: UA OSP - Invalid host header name or request url domain

geoffc;2499079 wrote:
On 4/30/2019 10:04 AM, gtejo wrote:
>
> geoffc;2499018 Wrote:
>> On 4/29/2019 5:16 PM, gtejo wrote:
>>>
>>> They already have those, since before the upgrade the ua was working,
>>> they have the same certificates. Now i modified the setenv of the

>> tomcat
>>> to set the logging of the OSP in ALL. This is what i see, the error

>> is
>>> clear but even if i change the URL in the configupdate i get the same
>>> error. Any clue?
>>> [image: https://i.imgur.com/zftOeWQ.png]

>>
>> Why would you not paste that as text, instead posting as a screen shot?
>> You reduce the amount of help you will get by pasting as screen shot.
>>
>> Does your /etc/hosts define the full DNS name of the server for its IP?

>
> Thanks for the recommendation, next time I'll use the text. Yes it does,
> the host has the IP of the server and the DNS that IDM uses.


More sepcificaly, I was asking if the entry looks something like this:

10.1.1.1 serverName servername.acme.com

Not just
10.1.1.1 serverName


Yes it does, exactly like this 10.1.1.1 serverName servername.acme.com
0 Likes
gtejo1 Absent Member.
Absent Member.

Re: UA OSP - Invalid host header name or request url domain

Here is more info:
- This is how the OSP loads the HTTPInterface's

<HTTPInterface>:
Id: localhost
DisplayName: localhost
Enabled: true
Resolvable: true
Domain name: localhost
Port: 80
TLS: false
Cookie domain: localhost
<HTTPInterface>:
Id: 127.0.0.1
DisplayName: 127.0.0.1
Enabled: true
Resolvable: true
IP address: 127.0.0.1
Port: 80
TLS: false
Cookie domain: 127.0.0.1
<HTTPInterface>:
Id: idmv45dyt
DisplayName: idmv45dyt
Enabled: true
Resolvable: true
Domain name: idmv45dyt
Port: 80
TLS: false
Cookie domain: idmv45dyt
<HTTPInterface>:
Id: 192.168.172.28
DisplayName: 192.168.172.28
Enabled: true
Resolvable: true
IP address: 192.168.172.28
Port: 80
TLS: false
Cookie domain: 192.168.172.28


-This is the line of the DNS in the hosts file:
192.168.172.28 idmv45dyt idmv45dyt.bvsa.local


So i think that the problem is that there are not an HTTPInterface with the Domain name idmv45dyt.bvsa.local and the port 8543. I triying to look at where the OSP loads this interfaces, but i cant find the file.
0 Likes
Knowledge Partner
Knowledge Partner

Re: UA OSP - Invalid host header name or request url domain name

On 5/2/2019 12:14 PM, gtejo wrote:
>
> Here is more info:
> - This is how the OSP loads the HTTPInterface's
>>
>> <HTTPInterface>:
>> Id: localhost
>> DisplayName: localhost
>> Enabled: true
>> Resolvable: true
>> Domain name: localhost
>> Port: 80
>> TLS: false
>> Cookie domain: localhost
>> <HTTPInterface>:
>> Id: 127.0.0.1
>> DisplayName: 127.0.0.1
>> Enabled: true
>> Resolvable: true
>> IP address: 127.0.0.1
>> Port: 80
>> TLS: false
>> Cookie domain: 127.0.0.1
>> <HTTPInterface>:
>> Id: idmv45dyt
>> DisplayName: idmv45dyt
>> Enabled: true
>> Resolvable: true
>> Domain name: idmv45dyt
>> Port: 80
>> TLS: false
>> Cookie domain: idmv45dyt
>> <HTTPInterface>:
>> Id: 192.168.172.28
>> DisplayName: 192.168.172.28
>> Enabled: true
>> Resolvable: true
>> IP address: 192.168.172.28
>> Port: 80
>> TLS: false
>> Cookie domain: 192.168.172.28

>
> -This is the line of the DNS in the hosts file:
>> 192.168.172.28 idmv45dyt idmv45dyt.bvsa.local

>
> So i think that the problem is that there are not an HTTPInterface with
> the Domain name idmv45dyt.bvsa.local and the port 8543. I triying to
> look at where the OSP loads this interfaces, but i cant find the file.


It is buried deep in the JAR as a config text file, but it uses
variables set, usually earlier in the ism-configuration.properties file.
Or else by code. I.e. It is not explicit in the deeper buried file,
rather it is referenced usually. (Not sure about this very specific
example, but in general).


0 Likes
gtejo1 Absent Member.
Absent Member.

Re: UA OSP - Invalid host header name or request url domain

So i think i need a way to add a new interface, or by default, modify one. If this configuration is in one of the jar files that the OSP uses, i dont think that digging into the jar files is a viable solution. So if the HTTPInterfaces are defined by a code, i think that the code should pickup the input values from one of the configuration places that OSP use, or the certicates, or the ism-configuracion.properties. I verified all the certificates in the two keystores (eDirectory and OSP) and the certificates in the keystore that tomcat uses. Also verified the server.xml and the ism-configuracion.properties file, in there i have a lot of configuration parameters, but not one let me define witch HTTPInterface the OSP uses.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.