@SNP said:
I have the same problem in 1.20, can some one help me where i find where this javascrip are in 1.20.
(From a big fan of fog, fog has saved us a lot of time.)
For fog 1.20, files are located at:
fog/management/ajax/login.info.php <- Comment out entire page after <?php
fog/lib/fog/ProcessLogin.class.php <- Comment out lines 230-233 and 244
@Tom-Elliott Thank you for providing a solution for this. I will test it tomorrow. I think if i found the right file before, i could have fixed it myself :). Thanks to all for the great support. I will reply tomorrow containing the results.
@Sebastian-Roth said in FOG Login with spaces in username:
@kek said in FOG Login with spaces in username:
but it is also is not working because the LDAP Plugin looks if this username exists in the AD but this name does only exists in the web page field in some users.
Can you be more specific on how you know this? You seem to have a lot of detail knowledge about how this works but you don’t post any of the details. Please share more of the information here.
I made a lot of error_logs to see what the Plugin is searching for, but then i saw the Plugin is not the problem.
I know that because the user got put in the Database after i tried to login a user, but it is not logging in.
Reading between the lines I guess you have looked through the FOG (LDAP plugin) code already.
Yes i looked in the LAP Plugin code to see what is the problem, but as already said the Plugin does it’s Job right.
I error_log ged the search thats is executed when you try to Login.
Please let us know where you see it’s doing the wrong thing.
The problem lies by the FOG Login, and because i dont see in the Code why spaces aren’t allowed i made that post.
I think this PHP Class is for the login: processlogin.class.php
@Sebastian-Roth said in FOG Login with spaces in username:
@kek said in FOG Login with spaces in username:
Yes i put the username in that field with a dot instead of a space but it is also not working.
What do you mean by that?
I thought i could put the username separated with a dot in the Web Page field in the AD user properties page because only some persons need access to the FOG Server, but it is also is not working because the LDAP Plugin looks if this username exists in the AD but this name does only exists in the web page field in some users.
@Sebastian-Roth said in FOG Login with spaces in username:
@kek said in FOG Login with spaces in username:
I tried already another User Name Attribute like wWWHomePage but it does also not work.
Also because of spaces??
Yes i put the username in that field with a dot instead of a space but it is also not working.
@Quazz said in FOG Login with spaces in username:
Underscores do work I believe, if that’s an option for you.
Because we have only spaces in usernames in our infrastructure we can only get that to work with spaces supported.
I tried already another User Name Attribute like wWWHomePage but it does also not work.
I activated the LDAP Plugin and connected it to an Microsoft AD but i can only login when there are no spaces in the usernames. I found out that the LDAP Plugin does its work perfectly but FOG itself can’t process the login after validation. I tried to create an user locally and it says ‘Invalid Input’ when there is a space.
Thanks for the help in advance.
@Sebastian-Roth Thank you for your help, sorry for the late reply was very busy in the last weeks.
I managed it with turning on/off the no menu option.
I created a Advanced Menu through FOG Configuration -> iPXE Menu Settings -> Advanced Menu Settings
But i only want to be able to access the menu when a host is not registered.
But with the option No Menu in General Configuration activated when i try to access the Advanced Menu from the main Menu it boots directly from the Hard Drive.
I’m a noob in php but i think i found the file that needs editing: /var/www/fog/lib/fog/bootmenu.class.php
But i have not found the section that needs editing.
Here is my custom menu:
:MENU
menu
colour --rgb 0xff0000 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap Admin Menu
item --gap -- -------------------------------------
item fog.local Starte von Festplatte wenn keine Auswahl...
item fog.memtest Memtest86+
item Gparted Gparted Live
item fog.sysinfo Client System Information (Kompatibel-Check)
item fog.return <- Hauptmenu
:fog.local
sanboot --no-describe --drive 0x80 || goto MENU
:fog.memtest
kernel memdisk initrd=memtest.bin iso raw
initrd memtest.bin
boot || goto MENU
:Gparted
kernel http://${fog-ip}/html/iso/gparted/live/vmlinuz vmlinuz boot=live config components union=overlay username=user noswap noeject ip= vga=788 fetch=${fog-ip}/html/iso/gparted/live/filesystem.squashfs
initrd http://${fog-ip}/html/iso/gparted/live/initrd.img
boot || goto MENU
:fog.sysinfo
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://10.10.0.20/fog/ consoleblank=0 rootfstype=ext4 storage=10.10.0.20:/images/ storageip=10.10.0.20 loglevel=4 mode=sysinfo
imgfetch init_32.xz
boot || goto MENU
:fog.return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} || prompt
goto MENU
@Tom-Elliott said:
@Mats-Nilsson said:
Problem solved. I installed a complementary Java Based Offline Proxy Server… [url]http://www.proxy-offline-browser.com/[/url]
(Java was bundled in Ubuntu) proxy ip 127.0.0.1 and port 8080 in Fog configuration and Firefox settings
I consider Fog to complex to be modified according to my wishes. It is clearly built to be online. To much workProblem solved as stated.
However, your information is correct. I just wanted to know why the revival, are you having the issue?
I was having the issue, hence the reason I ended up on this page. I prefer the original method mentioned earlier in the page for an earlier version of fog without needing to download additional software. A question was raised regarding the newer version of fog, one to which an answer would have saved me some time. Upon finding the solution, I posted the results for anyone that comes upon this page to save time of their own. I honestly didn’t want to bring up a discussion, rather, just an FYI note for future viewers. The information I provided is valid and would be quite useless in a new thread.
@Tom-Elliott said:
@kek Reviving an old thread?
Old thread or not, it is the first google search result with no valid solutions or otherwise help for version 1.20. Just thought I’d update it.