import org.lastaflute.web.login.exception.LoginFailureException;
import org.lastaflute.web.response.ActionResponse;
import org.lastaflute.web.response.HtmlResponse;

/**
 * SSO (Single Sign-On) action controller.
 *
 * This action handles SSO authentication flows including login, logout, and metadata
 * operations. It coordinates with the SsoManager to perform authentication using

    int NT_STATUS_BAD_NETWORK_NAME = 0xC00000cc;
    /** No more connections can be made to this remote computer */
    int NT_STATUS_REQUEST_NOT_ACCEPTED = 0xC00000d0;
    /** Indicates a domain controller could not be contacted or objects are protected */
    int NT_STATUS_CANT_ACCESS_DOMAIN_INFO = 0xC00000da;
    /** The specified domain does not exist */
    int NT_STATUS_NO_SUCH_DOMAIN = 0xC00000df;

            // this is not too good, probably should better pass the address and check that it is a netbios one.
            // While we could look up the domain controller/KDC we cannot really make the java kerberos implementation
            // use a KDC of our choice.
            // A potential workaround would be to try to get the server FQDN by reverse lookup, but this might have

            this.dcListExpiration = 0;
        } while (retry-- > 0);

        this.dcListExpiration = now + 1000 * 60 * 15; /* 15 min */
        throw new UnknownHostException("Failed to negotiate with a suitable domain controller for " + domain);
    }

    private static NtlmChallenge interrogate(final CIFSContext tf, final Address addr) throws SmbException {
        final UniAddress dc = new UniAddress(addr);

* GCE/Windows: disable stackdriver logging agent to prevent node startup failures ([#76099](https://github.com/kubernetes/kubernetes/pull/76099), [@yujuhong](https://github.com/yujuhong))

     * Before upgrading to 1.2, <strong>delete all Deployment alpha-version resources</strong>, including the Replication Controllers and Pods the Deployment manages. Then
create Deployment Beta resources after upgrading to 1.2. Not deleting the
Deployment objects may cause the deployment controller to mistakenly match
other pods and delete them, due to the selector API change.

* Nginx
    * С дополнительным компонентом типа Certbot для обновления сертификатов
* HAProxy
    * С дополнительным компонентом типа Certbot для обновления сертификатов
* Kubernetes с Ingress Controller похожим на Nginx
    * С дополнительным компонентом типа cert-manager для обновления сертификатов
* Использование услуг облачного провайдера (читайте ниже 👇)

        assertEquals(NbtAddress.SMBSERVER_NAME, nbtAddress.firstCalledName());

        mockName = new Name(mockConfig, "DOMAIN", 0x1C, null); // Domain Controller
        nbtAddress = new NbtAddress(mockName, testAddressInt, false, NbtAddress.H_NODE);
        assertEquals(NbtAddress.SMBSERVER_NAME, nbtAddress.firstCalledName());

        int[] versionMinors = { 1, 0, 0 };
        int[] serverTypes = { 0x00000801, 0x00000809, 0x0000101B }; // Various server types
        String[] comments = { "Workstation", "File server", "Domain Controller" };

        // Set converter and number of entries
        setConverter(response, 0);
        setNumEntries(response, numServers);

        // Calculate total buffer size

* Nginx
    * Mit einer externen Komponente wie Certbot für Zertifikat-Erneuerungen
* HAProxy
    * Mit einer externen Komponente wie Certbot für Zertifikat-Erneuerungen
* Kubernetes mit einem Ingress Controller wie Nginx
    * Mit einer externen Komponente wie cert-manager für Zertifikat-Erneuerungen
* Es wird intern von einem Cloud-Anbieter als Teil seiner Dienste verwaltet (siehe unten 👇)