All Downloads are FREE. Search and download functionalities are using the official Maven repository.

schemas.FedizConfig.xsd Maven / Gradle / Ivy

There is a newer version: 1.7.0
Show newest version



    
        
            
                
            
        
    

    
        
            
                
                
                
                
                
                
                
                
                
                
                
                
                
                
                
                
                
            
            

        
    

    
        
            
                
            
        
    

    
        
        
        
    

    
        
            
                
            
        
    

    
        
            If a SAML token contains a audience restriction which is not listed
                within this collection,
                the token will be refused.
            
        
        
            
                
            
        
    

    
        
            Valid value within the SAML token audience restriction element.
        
    

    

    
        
            
            
        
    

    

    
        
            Decision whether the token validation (e.g. lifetime) shall be
                performed on every request
                (true) or only once at initial authentication (false).
            
        
    
    
    
        
            Whether to add the "Authenticated" role to the list of roles associated
            with the "authenticated" user. This could be useful if you don't care about authorizing 
            the user, only about authentication. A role is required to activate authentication, and it
            may be problematic to list all relevant roles in web.xml. Note that if the user has no
            roles, then the "Authenticated" role is added automatically.
            
        
    

    

    

    
        
            Signing key required to generate a XML signature element within the federation
                metadata
                document, as well as for generating a signed signin request.
            
        
    

    

    

    
        
            User defined logout URL to trigger federated logout process. This URL will be
                available in
                addition to the 'wa=wsignout1.0' URL parameter.
                If the URL is overlapping an existing resource URL, the
                logout handling will be performed instead of
                accessing the resource.
                Example: '/logout'
            
        
    

    
        
            URL to landing-page after successful logout.
                Example: '/index.jsp'
            
        
    
    
    
        
            
                
                    
                    
                    
                    
                    
                
                
            
        
    

    
        
            
                
                    
                    
                    
                    
                    
                    
                    
                
                
            
        
    

    
    
    
    
    

    
    
    
    
    
    
    

    
        
            
            
            
            
            
            
            
            
            
            
        
    
    
     
        
            
                
            
        
    
    
    
        
            
            
        
    

    
        
            
                
            
        
    
    
    
        
            A regular expression constraint on the 'wreply' parameter, which is used to obtain the URL to 
                navigate to after successful logout. If the constraint is not specified, then the 'wreply' parameter is ignored 
                and instead the URL is taken from the "logoutRedirectTo" configuration option.
                Example: 'https://localhost:12345/logout.*/'. Alternatively it can be specified in a CallbackHandler
            
        
    

    
    
    
    
    
    
    
    
    

    
        
            
            
        
    

    
        
            
                
            
        
    

    
        
            
            
        
    

    
        
            
                
            
        
    

    
        
    


    
        
            
                This structure contains the specification of JSSE
                TrustManagers for
                a single Keystore used for trusted certificates.
            
        
        
            
                
                    
                        This element contains the KeyStore used as a
                        trust
                        store.
                    
                
            
        
        
            
                
                    This attribute contains the KeyManagers provider
                    name.
                
            
        
        
            
                
                    This attribute contains the algorithm the KeyManagers Factory
                    will use in creating the KeyManagers from the KeyStore. Most
                    common examples are "PKIX".
                
            
        
    

    
        
            
                A KeyStoreType represents the information needed to
                load a collection
                of key and certificate material from a desired
                location.
                The "url", "file", and "resource" attributes are intended
                to be
                mutually exclusive, though this assumption is not encoded in
                schema.
                The precedence order observed by the runtime is
                1) "file", 2)
                "resource", and 3) "url".
            
        
        
            
                
                    This attribute specifies the type of the keystore.
                    It is highly correlated to the provider. Most common examples
                    are
                    "jks" "pkcs12".
                
            
        
        
            
                
                    This attribute specifies the integrity password for
                    the keystore.
                    This is not the password that unlock keys within the
                    keystore.
                
            
        
        
            
                
                    This attribute specifies the keystore
                    implementation provider.
                    Most common examples are "SUN".
                
            
        
        
            
                
                    This attribute specifies the URL location of the
                    keystore.
                    This element should be a properly accessible URL, such as
                    "http://..." "file:///...", etc. Only one attribute of
                    "url",
                    "file", or "resource" is allowed.
                
            
        
        
            
                
                    This attribute specifies the File location of the
                    keystore.
                    This element should be a properly accessible file from the
                    working directory. Only one attribute of
                    "url", "file", or
                    "resource" is allowed.
                
            
        
        
            
                
                    This attribute specifies the Resource location of
                    the keystore.
                    This element should be a properly accessible on the
                    classpath.
                    Only one attribute of "url", "file", or "resource" is
                    allowed.
                
            
        
    

    
        
            
                A CertStoreType represents a catenated sequence of
                X.509 certificates,
                in PEM or DER format.
                The "url", "file", and
                "resource" attributes are intended to be
                mutually exclusive, though
                this assumption is not encoded in schema.
                The precedence order
                observed by the runtime is
                1) "file", 2) "resource", and 3) "url".
            
        
        
            
                
                    This attribute specifies the File location of the
                    certificate store.
                    This element should be a properly accessible file
                    from the working directory. Only one attribute of
                    "url", "file", or
                    "resource" is allowed.
                
            
        
        
            
                
                    This attribute specifies the Resource location of
                    the certificate store.
                    This element should be a properly accessible
                    on the classpath.
                    Only one attribute of "url", "file", or "resource"
                    is allowed.
                
            
        
        
            
                
                    This attribute specifies the URL location of the
                    certificate store.
                    This element should be a properly accessible URL,
                    such as
                    "http://..." "file:///...", etc. Only one attribute of
                    "url", "file", or "resource" is allowed.
                
            
        
    



    
        
            
                This structure specifies the JSSE based KeyManagers
                for a single Keystore.
            
        

        
            
                
                    
                        This element specified the Keystore for these
                        JSSE KeyManagers.
                    
                
            
        
        
            
                
                    This attribute contains the password that unlocks
                    the keys within the keystore.
                
            
        
        
            
                
                    This attribute contains the alias of the selected
                    key within the keystore.
                
            
        

        
            
                
                    This attribute contains the KeyManagers provider name.
                
            
        
        
            
                
                    This attribute contains the algorithm the KeyManagers Factory
                    will use in creating the KeyManagers from the KeyStore. Most
                    common examples are "PKIX".
                
            
        
    

    
        
            Decision whether the received state must match the
                state saved in the context.
            
        
    






© 2015 - 2024 Weber Informatics LLC | Privacy Policy