http(s) authentification : how to pass informations ?
|
2019-05-05, 19:25
Post: #1
|
|||
|
|||
http(s) authentification : how to pass informations ?
Hello, I failed to find documentation about that and rare traces found on the forum are like this :
Code: https://${username:uristring}:${password:uristring}@${net0.dhcp/next-server}/pxe/menu.php How are ${username:uristring} and ${password:uristring} populated in this case ? Is it possible to prompt the user for these informations ? Is there a list of all variables iPXE sets itself that could be passed to a request ? |
|||
2019-05-06, 20:59
(This post was last modified: 2019-05-06 21:00 by NiKiZe.)
Post: #2
|
|||
|
|||
RE: http(s) authentification : how to pass informations ?
searching for ipxe username finds the example, see http://ipxe.org/cmd/login
If you use the example I would strongly suggest using netX instead of net0 Use GitHub Discussions VRAM bin |
|||
2019-05-11, 19:54
Post: #3
|
|||
|
|||
RE: http(s) authentification : how to pass informations ?
(2019-05-06 20:59)NiKiZe Wrote: searching for ipxe username finds the example, see http://ipxe.org/cmd/login Where netX would use anything available while net0 would use specifically the NIC that got that ID ? |
|||
2019-05-11, 20:06
Post: #4
|
|||
|
|||
RE: http(s) authentification : how to pass informations ?
net0 would use net0
while netX would use the last opened interface http://git.ipxe.org/ipxe.git/commitdiff/eba6bb3 if you start ipxe with native drivers and have 4 interfaces it runs the autoboot cmd internally which tries each interface in turn until it succeeds and gets a filename. let's say that it is net3 than netX would be the same as net3 but when writing the script we don't know this and if it was written with net0 than it would fail. there for, if you expect to be working with one interface only, then always use netX and not net0 Use GitHub Discussions VRAM bin |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 2 Guest(s)