* This factory maintains a registry of data store implementations and provides methods
 * to register, retrieve, and discover available data stores.
 *
 * <p>Data stores are registered by name and class name, allowing flexible lookup.
 * The factory also supports dynamic discovery of data store plugins by scanning
 * JAR files for data store configurations.</p>
 *

                }
            }
        } catch (SocketException e) {
            log.error("Failed to discover local interfaces", e);
        }

        // Sort by score
        localInterfaces.sort((a, b) -> Integer.compare(b.getScore(), a.getScore()));

        log.debug("Discovered {} local network interfaces", localInterfaces.size());
    }

    private boolean canEnableMultiChannel() {

        * `password`: some next chapters will cover examples of this.
* `openIdConnect`: has a way to define how to discover OAuth2 authentication data automatically.
    * This automatic discovery is what is defined in the OpenID Connect specification.


/// tip

For **TypeScript clients**, <a href="https://heyapi.dev/" class="external-link" target="_blank">Hey API</a> is a purpose-built solution, providing an optimized experience for the TypeScript ecosystem.

You can discover more SDK generators on <a href="https://openapi.tools/#sdk" class="external-link" target="_blank">OpenAPI.Tools</a>.

/// tip

     *     <li>"release_or_snapshot" - the default</li>
     *     <li>"release" - query only release repositories to discover versions</li>
     *     <li>"snapshot" - query only snapshot repositories to discover versions</li>
     * </ul>
     * Default (when unset) is existing Maven behaviour: "release_or_snapshots".
     * @since 4.0.0
     */

public void initializeWitnessSupport() {
    Configuration config = context.getConfig();
    
    if (!config.isUseWitness()) {
        return;
    }
    
    try {
        // Discover witness service
        InetAddress witnessServer = discoverWitnessService();
        if (witnessServer != null) {
            witnessClient = new WitnessClient(witnessServer, context);
            witnessEnabled = true;

            log.info("Server does not support multi-channel");
            return;
        }
        
        // Query network interfaces from server
        queryRemoteInterfaces();
        
        // Discover local interfaces
        discoverLocalInterfaces();
        
        // Enable multi-channel if we have multiple usable interfaces
        if (canEnableMultiChannel()) {
            multiChannelEnabled = true;

        List<RelatedQuery> testData = new ArrayList<>();
        testData.add(createRelatedQuery("search", new String[] { "find", "lookup" }, "site1.com"));
        testData.add(createRelatedQuery("search", new String[] { "query", "discover" }, "site2.com"));
        mockBhv.setTestData(testData);

        relatedQueryHelper.load();

        // Mock virtual host helper to return site1.com
        virtualHostHelper = new VirtualHostHelper() {

            log.warn("Failed to initialize witness support", e);
        }
    }

    /**
     * Discover witness service for the current server
     *
     * @return witness server address or null if not found
     * @throws IOException if discovery fails
     */
    private InetAddress discoverWitnessService() throws IOException {
        // Try the same server first

After a week, the token will be expired and the user will not be authorized and will have to sign in again to get a new token. And if the user (or a third party) tried to modify the token to change the expiration, you would be able to discover it, because the signatures would not match.

If you want to play with JWT tokens and see how they work, check <a href="https://jwt.io/" class="external-link" target="_blank">https://jwt.io</a>.