Hello
I would like to simply protect a single page of my application with a password, is this possible?
simply protect a single page
Re: simply protect a single page
Hi,
not with AG possibilities at this time (afaik).
Just as a starting point:
You could use the /hooks/tablename.php -> _init function: Place some code there that
a) checks, if a session variable is set,
-> if yes, allow access to the page,
-> if no, set the return value to false and forward to another (custom) page (and set the return value to false). On that (custom) page ask for the password, if it's correct set the session variable, return to your (protected) page. If the password is wrong, stay on the password page.
Olaf
not with AG possibilities at this time (afaik).
Just as a starting point:
You could use the /hooks/tablename.php -> _init function: Place some code there that
a) checks, if a session variable is set,
-> if yes, allow access to the page,
-> if no, set the return value to false and forward to another (custom) page (and set the return value to false). On that (custom) page ask for the password, if it's correct set the session variable, return to your (protected) page. If the password is wrong, stay on the password page.
Olaf
Some postings I was involved, you might find useful:
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view
Re: simply protect a single page
Could you not protect using membership in a group (embed that protection in the hook for that table)? Then there login password would effectively be that page protection.
~Paul
~Paul
Re: simply protect a single page
Hi,
yes, Pauls solution sounds good too
Olaf
yes, Pauls solution sounds good too
Olaf
Some postings I was involved, you might find useful:
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view