Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Highlighted
sadhani Absent Member.
Absent Member.
400 views

Ability to use just the hostname in the proxy services


We have a client where the users are used to only typing the hostname
and the domain name is appended by the workstation configs.

So, we need to enable that functionality via NAM.

I tried using just the hostname in NAM, but NAM would not let me. When
I type just the hostname in the browser, I get a NAM 403 URL Tampering
error.
I found a cool solution for error.jsp page, which talks about
redirecting to the FQDN using a javascript, if just the hostname is
specified in the browser.
'Cool Solutions: Redirecting the Access Gateway to the Full Domain
Name' (http://www.novell.com/coolsolutions/tip/19793.html)

I tried that setting in the error.jsp page, and it took me to a
namproxyfailover error page. There isn't any proxy service defined for
namproxyfailover. So, I am wondering, what might cause this page to be
rendered. I even tried specifying redriection to 'Google'
(http://www.google.com) to see if NAM would redirect to a third-party
page (window.location.href = "http://www.google.com";). That did not
work either
Is there any other way that I might be able to implement the
redirection?


Thanks


--
sadhani
------------------------------------------------------------------------
sadhani's Profile: http://forums.novell.com/member.php?userid=102002
View this thread: http://forums.novell.com/showthread.php?t=451901

0 Likes
2 Replies
sadhani Absent Member.
Absent Member.

Re: Ability to use just the hostname in the proxy services


Correction. A proxy service does exist for namproxyfailover. So,
apparently, the redirection is not working at all.
The requests are to be ssl'ized, else we could use virtual multi-homing
and make it work.

I found this article, which speaks about using virtual multi-homing for
the non-SSL requests.

http://www.novell.com/communities/node/12197/novell-access-manager-%E2%80%93-%E2%80%9Cdetected-url-tampering%E2%80%9D

Since, the certs are based off of the full domain name, just specifying
the hostname will result in a certs authorization issue.

Any thoughts on how the redirection could be made to work in NAM?


--
sadhani
------------------------------------------------------------------------
sadhani's Profile: http://forums.novell.com/member.php?userid=102002
View this thread: http://forums.novell.com/showthread.php?t=451901

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Ability to use just the hostname in the proxy services

sadhani wrote:

>
> We have a client where the users are used to only typing the hostname
> and the domain name is appended by the workstation configs.


This kinda contradict with what you say below. According to you the
workstation config adds the domain name but that doesn't seem to
happening otherwise you wouldnt get the 403 error.

> So, we need to enable that functionality via NAM.
>
> I tried using just the hostname in NAM, but NAM would not let me. When
> I type just the hostname in the browser, I get a NAM 403 URL Tampering
> error.
> I found a cool solution for error.jsp page, which talks about
> redirecting to the FQDN using a javascript, if just the hostname is
> specified in the browser.
> 'Cool Solutions: Redirecting the Access Gateway to the Full Domain
> Name' (http://www.novell.com/coolsolutions/tip/19793.html)
>
> I tried that setting in the error.jsp page, and it took me to a
> namproxyfailover error page. There isn't any proxy service defined for
> namproxyfailover. So, I am wondering, what might cause this page to be
> rendered. I even tried specifying redriection to 'Google'
> (http://www.google.com) to see if NAM would redirect to a third-party
> page (window.location.href = "http://www.google.com";). That did not
> work either
> Is there any other way that I might be able to implement the
> redirection?


Hmm...not sure why this took you to namproxyfailover as the script
doesn't make any reference to it. The coolsolution seems somewhat
incomplete as I think the javascript bit is missing but not really sure.

What you can do in the if statement (from the coolsolution article that
is) is add some conditions that if host equals www then redirect to
www.test.com or something. There's plenty of info out there that'll
describe how to do that.



--
Cheers,
Edward
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.