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
Anonymous_User Absent Member.
Absent Member.
744 views

HTTP Status 404 - /nps/servlet/imanauthentication


I am now on my fourth server installation of SLES 11 SP2. In each case
after installing eDirectory 8.8.5, I have installed iManager 2.7 with
plugins 2.7.5 and eDirectory 8.8, and in each case iManager fails to log
in with the error above.
These are brand new installs. The installation logs are fine,
eDirectory works fine supporting GroupWise. Tomcat responds ok.
These servers are replacing Netware, but I am having to keep a Netware
server running just to be able to access that version of iManager. This
issue has been mentioned several times in the forums but nobody has come
forward with an answer. It would be nice to have it resolved.


--
konnovell
------------------------------------------------------------------------
konnovell's Profile: https://forums.netiq.com/member.php?userid=1964
View this thread: https://forums.netiq.com/showthread.php?t=3075

Labels (1)
0 Likes
7 Replies
Anonymous_User Absent Member.
Absent Member.

Re: HTTP Status 404 - /nps/servlet/imanauthentication


I found this problem when i install the Imanager, and i solved this
problem changing the web.xml file to newweb.xml; and change the
newweb.xml to web.xml the i restart the tomcat and everything is fine
(A coworker coment this solution)

I wait the this solve your problem

Best Wishes

konnovell;13198 Wrote:
> I am now on my fourth server installation of SLES 11 SP2. In each case
> after installing eDirectory 8.8.5, I have installed iManager 2.7 with
> plugins 2.7.5 and eDirectory 8.8, and in each case iManager fails to log
> in with the error above.
> These are brand new installs. The installation logs are fine,
> eDirectory works fine supporting GroupWise. Tomcat responds ok.
> These servers are replacing Netware, but I am having to keep a Netware
> server running just to be able to access that version of iManager. This
> issue has been mentioned several times in the forums but nobody has come
> forward with an answer. It would be nice to have it resolved.



--
sagonzalez
------------------------------------------------------------------------
sagonzalez's Profile: https://forums.netiq.com/member.php?userid=2142
View this thread: https://forums.netiq.com/showthread.php?t=3075

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: HTTP Status 404 - /nps/servlet/imanauthentication


Hey sorry, I only just got back to this - I thought nobody was
responding out there.
You are dead right, my friend, but who would have known it? I expected
it to connect out of the box!
Perhaps I should have investigated further myself. I can see the
authentication mapping is in the newweb.xml but not in the web.xml.
That's great. The mystery is solved for anybody else out there. Thank
you.

Kevin.


--
konnovell
------------------------------------------------------------------------
konnovell's Profile: https://forums.netiq.com/member.php?userid=1964
View this thread: https://forums.netiq.com/showthread.php?t=3075

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: HTTP Status 404 - /nps/servlet/imanauthentication


I'm getting the same error, but on Windows...
What is the whole path of the web.xml and newweb.xml?
I tried doing this, whitout success in the default folder installation
(C:\Program Files (x86)\Novell\Tomcat\webapps\nps\WEB-INF\

Thanks in advance.
JP


--
jpgalocha
------------------------------------------------------------------------
jpgalocha's Profile: https://forums.netiq.com/member.php?userid=2741
View this thread: https://forums.netiq.com/showthread.php?t=3075

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: HTTP Status 404 - /nps/servlet/imanauthentication


konnovell;13198 Wrote:
> I am now on my fourth server installation of SLES 11 SP2. In each case
> after installing eDirectory 8.8.5, I have installed iManager 2.7 with
> plugins 2.7.5 and eDirectory 8.8, and in each case iManager fails to log
> in with the error above.
> These are brand new installs. The installation logs are fine, eDirectory
> works fine supporting GroupWise. Tomcat responds ok.
> These servers are replacing Netware, but I am having to keep a Netware
> server running just to be able to access that version of iManager. This
> issue has been mentioned several times in the forums but nobody has come
> forward with an answer. It would be nice to have it resolved.


Just to add something here. I've been able to replicate this reliably.
On a fresh clean install, if you download the sp5 for iManager during
the install I get this issue. Looking at the logs it appears that it
installs sp5 npm, then lays the older iman npm on top if it. (messing up
the web.xml)

A re-install without the service pack, then adding it later via iman
plugin download seems to do the trick for me. Just my .02.


--
markgard
------------------------------------------------------------------------
markgard's Profile: https://forums.netiq.com/member.php?userid=347
View this thread: https://forums.netiq.com/showthread.php?t=3075

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: HTTP Status 404 - /nps/servlet/imanauthentication

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well found; I have duplicated this and have reported it to Novell. I'll
post back results as they come.

Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQIcBAEBAgAGBQJQktOMAAoJEF+XTK08PnB56nkP/2h4yuUrmSvh/VfUuYtKMwlK
2My3w9KSzzki1/Ey8mRB/v+NT4JaA8Ed6c9HrtNvdSTQQHSzBEvYmWbw0SC3OD66
vMYmdPV3c8UvFvjvMfYCRyii8oh2MOaHFq2EjJ1DwpPFfKr4PnatP71UL7DpBGHX
R5lqTJ9rXcLUqdNCMw+/n10c7DLjojP9v72LR5RXpbF0qamOxFGOj9N40j5Enwft
7Qe1rfuN9m+AW4ZqRzjjLGzOSuwpI5i7w32CqFGx/Poz8ZVkB1pvortwhNWxLa50
It1gupu1a02VhBrrcwsLHjURnbIrZP0sxZK/5do75ivy0lGbRFh1+J6Ddwx+TgRJ
ken+aJhf9IknAtCRiiAJcHDDQJWdCCQtIriEq8Y+KS8y0XjrtIRrEhQUA5qC7Kj6
tLT0WOBa+baoZB6VvqN1ztql2M0zXBA7w++82kHZQoH4IjLmVabQ4snAMvKO7gFX
E+UXU0t01dirmPQnhSbYgE4eBunWG8RNBrBxLAkfZWGobN/7bjmjrCoZp1+WgNW1
4BPAROPcahxvHLIqbhLf737w0HUgRlzpSOwwrhmxC+B+piMd5R+b7eWCmGAVM91z
rR040WFwxOZ7VZqVjR2r5iuFIQk+aNdwDcLWhUFAhtOMHfdNfHxGJodAEGpWd6b4
2FlEZrxCHPSlnQ0HzqyW
=sxUb
-----END PGP SIGNATURE-----
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: HTTP Status 404 - /nps/servlet/imanauthentication

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bug# 787760 reported for those interested.

Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQIcBAEBAgAGBQJQkwHeAAoJEF+XTK08PnB5ppkP/2t2Pdw+/QcVfCO1Fy+jlRDj
HjmNsGCzbnzIteOVhzYBgCHiKM8PjQTGnhuGW9O6HTDZyxxEIycE5re+kyJQElUf
FBWAO8MipjxR5lzw4mRrSqhrAly7djPF8CvowMAZZmZLrsc2Ge5XL+qV3+cqgvi6
LvaHENI5h75CNgU9EtZ/2hn+fwYfquPgq7H+tXZsI2fzs6fR2TQuFbOZ8za8EcNa
bGXO6tFXKpTwylfJMY5NDoshwc05DiTUUvu2C6uX5r/4fSey8SUhji/SSPop8uos
qGYtqSpHRMuXmhfq/gNqFecwvVDBqVukuRcyEUDx0q1G0tGqMHFJ+KeKowlB+R8W
UTLQR6isvvGykeNQAfwDK5G+qmUhVOYju39pBhAsxyt3r2zwuP0Mrw8Cf3xmyuGs
EWVRA2voJD+8mmA0iCfFV3graBrXkfJxAqWOanBSWWeF2CJrUWLqSSob4oydYnqg
Y92pGPMKSKQVUHDXkWpRmKTcWPHCaC6q4RCxwptmYk2FhZ6ut+3VR9ziCkGaF7OB
UOstZkqtKcWOqWpl6dTTeszZfK67kuOfWuS2MsY2sETxxL1ZCZ/gAmLZU+2nWTt4
JjtU2C8omUk7G8AHdBPdm0/ahYWxHkiud+IM+f9/pzAtl/V61zKP8fUBN7/+crO0
H9TZuMX1nn1Pk+lL/fvc
=jzLE
-----END PGP SIGNATURE-----
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: HTTP Status 404 - /nps/servlet/imanauthentication

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

TID# 7010490 worked for me in resolving this issue, btw. It looks like
this will be fixed in iManager 2.7 SP6.... somehow.

Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQIcBAEBAgAGBQJQl93GAAoJEF+XTK08PnB5nj8P/RNfW8A3RLEl5zcCGoA9PMoa
TLIW0Ygl5/zEAZZfrA7TFk6uTSzNrg34+ZKgxvQXHK6PjgtzoCIpnXoHEQqNdGaa
1JKv0ulq40c5jOYU7uM0FNAsykpE5LgGY+vHINFaMMTUvXOc6pvLVXUafZMMEN1Z
hqSclA/zZ6wjPWUDwnugSAakQd0dMrzNKzXtx7EvnNLVHvXlX7n4X67gr6478AiB
4KYD+4aHG3gG0DvFwONec/4DBC6Qm5wcUn0tv9EBFP5CtMkstwlG7z87J97A7PBQ
928EfFNo2FKIQFoawJTVT4pM7uSJr8mzNWzJeamjOCmkMgZwAR4t5+/ckSFvX3na
NMlUoKEqx2eYEWOmARP/kA0xFORLGUaZ4N4Tcdhj302LJJ4FGF9nJ1d6lR1MXwd0
0T83bC3VgO2i666KKtls/ulp4+f/o5L6fKFqmSykWaYyAmemWewIzxwbOzfqSfOY
2pDIvnHCYbm/Lk/Nu/TPAhVesb3776DY/I6h018RexR+Pt6OdkBx9uds4xhqPmK/
Cn/NLBgkyfGSH11XL2i+X0BHKYhXJnS5MNCQljWz4wZI3sP7TIu4yI31U+rtzxJq
VO1AB/qpT8oWoQ2Tv/3L7F8eSgwjUYfVnxxvw0NJKirqbHGVrSGUc+jHRbPHMCGR
1sTBwPB7gNmxn7Xut1Ex
=BCuf
-----END PGP SIGNATURE-----
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.