What is NOT part of configuring a federation for a custom ASP.net application with Okta?

When configuring federation for a custom ASP.NET application with Okta, certain steps and components are essential for establishing an effective connection and management of user identities. One of these components is the federation metadata file, which provides crucial information about the identity provider and is necessary for establishing trust between the service provider and the identity provider. Access control settings are also critical, as they define who can access the application and under what conditions. Additionally, setting up the service provider configuration is fundamental because it ensures that your ASP.NET application can correctly process authentication requests and responses.

However, database schema adjustments are not typically a part of the federation configuration process when using Okta. The federation approach operates primarily through standards like SAML or OpenID Connect, which focus on the exchange of authentication information using metadata, not requiring direct modification of the database schema within the ASP.NET application. Therefore, altering the database schema is unrelated to the configuration of federation with Okta, making it the correct choice for what is NOT part of this process.