Question

Web Access & Repositories

Ideas Web Client

Updated April 25, 2014

asked on April 23, 2014

Can the login page be changed so that the list of repositories are not shown? If you can just have the option to login and the site logs the user into their repository if they only have 1 repository but if the user has more then 1 repository then they are presented with a list of repositories that the user access too.

Reason is: If you wanted to have Laserfiche as a hosted service, you don't want your customers to see that they are sharing a server with other customers or know who your other customers are.

0 0

Answer

APPROVED ANSWER

replied on April 24, 2014

Hi Andrew,

Currently there isn't a way to hide the list of available repositories from users in Web Access because, as a web based product, the browser doesn't know which repository the user needs to access without first checking their credentials.

A solution for you could be providing different URLs for different repositories rather than an overarching URL for login. For example, http://localhost/laserfiche/Login.aspx?db=LaserRepository is the URL for a repository (called LaserRepository) in my test environment. That last part of the URL that says "db=RepositoryName" could be changed for each repository you want to provide access to. When a user goes to a URL with this specification, Web Access will default the repository selection.

1 0

Replies

replied on April 24, 2014 • Show version history

if they only have 1 repository but if the user has more then 1 repository then they are presented with a list of repositories that the user access too

The reasons we can't currently support this are:

the user hasn't authenticated yet when they get to the login page
there isn't a way to know if a user has access to a particular repository (without some credentials to use, either the user's or an administrator's)

We do have ideas to address this for hosted situations like you are talking about, but solving it correctly requires a bit of infrastructure work.

Kelsey's solution should work. Another solution is to make separate virtual directories for each client, and for each one only register their repository.

0 0

You are not allowed to follow up in this post.

Question

Question

Web Access & Repositories

Answer

Replies

Sign in to reply to this post.