-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no autologin #76
Comments
Hi Herbert, public function hasPermissionFor($key)
{
+ return TRUE;
$role = $this->container->session->get('role'); EDIT |
Guten ABend,
erstmal danke für die Mühen. Das Teil ist wirklich gut gemacht. Die Lösung in der Auth.php den Befehl "return TRUE;" zu setzen hat leider trotz Neustart nichts bewirkt. Es kommt immer die Anmeldung.
mfg
H. Springer
Gesendet: Sonntag, 10. November 2019 um 09:34 Uhr
Von: "othmar52" <[email protected]>
An: othmar52/slimpd <[email protected]>
Cc: truderinger <[email protected]>, Author <[email protected]>
Betreff: Re: [othmar52/slimpd] no autologin (#76)
Hi Herbert,
The user stuff is not finished yet.
I know it's really annoying to have the login form on every browser start.
Maybe i will fix this soon but i can't promise.
As a quick and dirty workaround add this sigle line to
core/php/Modules/Auth/Auth.php
public function hasPermissionFor($key)
{
+ return TRUE;
$role = $this->container->session->get('role');
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hallo,
and a great thanyou for the slimpd.
My config.ini say 👍
[users]
allow_empty_password = 0
always_show_guest_usernames = 0
I tried the three lines with various numbers and also with comment out. Unfortunately, always a login is requested. Since the part "headless" is in the living room and has no keyboard or mouse. Should the slimp server automatically log in itself?
Thanks for help.
bestregards
Herbert
The text was updated successfully, but these errors were encountered: