**
Remedy Knowledge Management 7 + Apache 2.2.3 + Tomcat 5.5 + modjk 1.2.19 + 1.5.0.8 JRE (whew) have made resolved the authentication issue listed below.  (We were running ServletExec+IIS6+1.4jre)

Oh, the wonders of open source.

And, wow... look how fast it is!

:=)

Happy early Friday everyone.  I'll hopefully see some of you out at the CMDB class in Pleasanton next week.

-tony


--
Tony Worthington
[EMAIL PROTECTED]
262-703-5911



Tony Worthington/Corp/Kohls

09/25/2006 01:34 PM

To
arslist@ARSLIST.ORG
cc
Subject
Re: Remedy Knowledge Management v7 ... grrrLink




Michiel -

Thanks for the response...

1.  Nope -- any combination of accounts will do it.

2.  No.  If you happen to end up at the login page (session still active on webserver/servlet?) you're screwed.
3.  Point taken, but we do have shared PC's that multiple individuals could be using as part of their job (HD agents, some share desks over 3 shifts)

<rant>You would think something as simple as authentication would be addressed prior to RTM.  I'm not looking forward to finding other "as designed" "features" in the product.</rant>

-tony

--
Tony Worthington
[EMAIL PROTECTED]
262-703-6125



Michiel Beijen <[EMAIL PROTECTED]>
Sent by: "Action Request System discussion list(ARSList)" <arslist@ARSLIST.ORG>

09/25/2006 01:24 PM

Please respond to
arslist@ARSLIST.ORG

To
arslist@ARSLIST.ORG
cc
Subject
Re: Remedy Knowledge Management v7 ... grrr





** Tony,

my 2 cts (I must say I do not have experience with RKM)

First; this error is not nice and should not be there, and I feel it should be addressed in the next patch.

1. Does this only happen if you would log in first with an Admin account?
2. Does this only happen if you log in the second time with a different account than the first time?
3. How many users would you typically have who are likely to log out / disconnect from the system and in the same browser log in using another account?

If 1 or 2 are true, I guess the idea is that - while it is stil a nasty error - you should be able to run the app in production without too much trouble, because the people that will be using the Admin account or the people that will be using different KM accounts will typically be power users and can be instructed to avoid the issue.. right?

And btw I have seen other web-apps (also other knowledge management solutions) which are around for a couple of years and also 'feature' nasty login/logout behaviour, it is not limited to RKM only I'm afraid...

--
Michiel

On 9/25/06, Tony Worthington <[EMAIL PROTECTED]> wrote:
**
All -


I've encountered a reproducible error in RKM v7 and am wondering if anyone out there has the same problem.  I received a "resolution" from Support and will probably end up escalating this...



Using the web interface, authentication type seems to not matter.  I assume the same will happen using the AR integration (view fields) but I haven't gotten that far yet...


Steps to reproduce:


1. Open browser and log into RKM using "Admin" using http://<server>/rkm/

2. Close out IE completely without selecting logout

3. Reopen IE and navigate to RKM URL http://<server>/rkm/

4. Log in as someone other than the account in step 1

5. Notice the Access Denied page. (You are not logged in or do not have sufficient privileges to access this resource.  Please login to access this resource.)  

6. No account will work on this page as it is the static error page, not the login page.

7.  Enter the <server>/rkm/ URL in the browser

8. A _javascript_ "Not Found" popup shows.

9.  Try and do anything now.  You get the "Not Found" popup on every action.


The accounts specified above really don't matter...  I've tried and reproduced using the same account in steps 1 and 4.



The feedback provided by Remedy is:


"We are aware of this issue and will address it in the future.

In the meantime, as a workaround, please logout using the logout button.

Or clear the cache after you restart IE.

This should keep you in a working state.


This ticket will now be closed."


Even this workaround doesn't prove effective 100% of the time.  More often than not I have to reload the webapp.  And then when I do that, it breaks whatever database servlet/routine pulls up the the KB entries, and then I have to bounce IIS.


This defect is large enough to prevent us from putting RKM into production.


</rant> :-)


Suggestions/ideas?  (other than dumping rkm)


-tony


--
Tony Worthington

[EMAIL PROTECTED]
262-703-6125
__20060125_______________________This posting was submitted with HTML in it___

__20060125_______________________This posting was submitted with HTML in it___


__20060125_______________________This posting was submitted with HTML in it___

Reply via email to