We have a web-enabled database that most users access anonymously. We recently received a requirement to hide certain columns in our views from everyone but a small group. So the idea is to make these specific people log in so we can compute the column hide-when formula based on their username.
It’s been many years since I’ve done web stuff, so I’ve forgotten a lot, and never learned a lot of the newer stuff. If I recall, the first time an Anonymous user tries to open a design element (view, document, etc) that is not available to public access users, they are prompted to log in, and after successful authentication they are brought back to the element they were trying to open.
The problem for us is, our views ARE available to public access users. It’s just that certain columns need to be hidden based on the user’s name being in a field on the database profile document. So the user trying to open that view will not prompt for authentication. Thus we need to force it. My company uses basic authentication - there is no chance of getting session-based authentication implemented here. To the best of my knowledge, the only way to force authentication is to append ?login to the end of a URL. However, when the user logs in using the form that is presented, they are redirected to the server’s home page, rather than back to the database element they were trying to get at.
How can I force the ?login link to bring the user back to our database when they’ve successfully authenticated?