Am 15.12.22 um 16:44 schrieb Eric Graham:
Thanks, Rick, for the clarification. I dug into the code to double check
that HTTP basic auth is not used.
The API spec is here:
https://gitlab.isc.org/isc-projects/stork/-/blob/aa1036c20dd32eaeaa9675b329d8b704dbeeb718/api/users-paths.yaml#L1-L33
If
Thanks, Rick, for the clarification. I dug into the code to double check that
HTTP basic auth is not used.
The API spec is here:
https://gitlab.isc.org/isc-projects/stork/-/blob/aa1036c20dd32eaeaa9675b329d8b704dbeeb718/api/users-paths.yaml#L1-L33
If basic auth were in use, there would be a secu
Questions are venturing out of scope for Kea/Stork and are more with general
HTTP but will make a stab at getting you pointed in right direction.
In your second call, you are attempting to use HTTP basic authentication
(--user arg to curl) instead of sending the session cookie. As mentioned
ea
Am 14.12.22 um 17:22 schrieb Eric Graham:
I haven't used that platform before, so I don't know for sure, but you
might find it easier to authenticate for each query, depending on how
frequent they are.
Trying to figure out these calls now.
curl -k -c cookie.txt -X POST -H 'Content-Type: appli
>
> When the PD-pool lease gets renewed the hook does not have the single IP
> lease info which is used as nexthop for PD route.
Did the client renew the single IP lease at the same time or did the client
only renew the prefix perhaps renewing the single IP lease at a different time?
--
I
