Can RAM be configured to present a login challenge on search
Our RAM users are passing around links which are asset searches scoped to a community.
Ex: https://myramserver.com/ram/search/index.jsp?a=fGroup%2Cmy_community
When users are not logged in, no assets show up (this is unfortunate but expected). When they are logged in they do see the correct assets.
One user suggested to me that our RAM server used to present a login challenge on this url but no longer does. How can RAM be configured to require login before searches?
Ex: https://myramserver.com/ram/search/index.jsp?a=fGroup%2Cmy_community
When users are not logged in, no assets show up (this is unfortunate but expected). When they are logged in they do see the correct assets.
One user suggested to me that our RAM server used to present a login challenge on this url but no longer does. How can RAM be configured to require login before searches?
7 answers
Our RAM users are passing around links which are asset searches scoped to a community.
Ex: https://myramserver.com/ram/search/index.jsp?a=fGroup%2Cmy_community
When users are not logged in, no assets show up (this is unfortunate but expected). When they are logged in they do see the correct assets.
If you wish, it's possible to configure your server to allow that users not logged in can search for assets. Make this in Communities --> YourCommunity --> Users --> Individual Users --> All Users, editing the roles as you wish.
One user suggested to me that our RAM server used to present a login challenge on this url but no longer does. How can RAM be configured to require login before searches?
RAM was designed to be able to show assets even the users aren't logged in, once this is a feature I don't see any way "to force" yours users on viewing the login page.
If you change your URL to
https://myramserver.com/ram/secure/search/index.jsp?a=fGroup%2Cmy_community
it will present the login page to the user before displaying search results. There is no configuration setting in RAM that will force users to login when accessing the search page.
I changed my urls to be based on
https://server.com/ram/secure/search/index.faces
This does prompt for login as you suggested. However after login I do not get search results, rather I get an error page.
Firefox gives me:
Content Encoding Error - The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression.
Chrome gives me:
The webpage at https://server.com/ram/secure/search/index.faces might be temporarily down or it may have moved permanently to a new web address.
Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error.
This is on RAM 7.5.0.1
If you're running WAS 7 you are most likely seeing the content encoding error due to this defect. There may be more information in your ramDebug.log file.
https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/45367
Does it work for URLs that contain parameters which specify search criteria? I receive a 404 for the URL
https://server.com/ram/secure/search/index.faces
but when I try the test for a URL the specifies search criteria it works.
https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/45367
Does it work for URLs that contain parameters which specify search criteria? I receive a 404 for the URL
https://server.com/ram/secure/search/index.faces
but when I try the test for a URL the specifies search criteria it works.
Rich, Sheehan, thanks for your replies. FYI I am on WAS 6.1 with a pretty recent fixpack (35?)
Here's the results of some experiments I did with urls from Chrome.
General search:
https://csnext.ibm.com/ram/secure/search/_rlvid.jsp.faces?_rap=_rlnn&_rvip=/search/index.jsp (works)
Community scoped search:
https://csnext.ibm.com/ram/secure/search/index.jsp?a=fGroup%2Clotus_connections_java_api (fails)
https://csnext.ibm.com/ram/secure/search/_rlvid.jsp.faces?_rap=_rlnn&_rvip=/search/index.jsp&a=fGroup%2Clotus_connections_java_api (works)
https://csnext.ibm.com/ram/secure/search/_rlvid.jsp.faces?a=fGroup%2Clotus_connections_java_api (fails)
Here's the results of some experiments I did with urls from Chrome.
General search:
https://csnext.ibm.com/ram/secure/search/_rlvid.jsp.faces?_rap=_rlnn&_rvip=/search/index.jsp (works)
Community scoped search:
https://csnext.ibm.com/ram/secure/search/index.jsp?a=fGroup%2Clotus_connections_java_api (fails)
https://csnext.ibm.com/ram/secure/search/_rlvid.jsp.faces?_rap=_rlnn&_rvip=/search/index.jsp&a=fGroup%2Clotus_connections_java_api (works)
https://csnext.ibm.com/ram/secure/search/_rlvid.jsp.faces?a=fGroup%2Clotus_connections_java_api (fails)