The Legacy Authentication Provider represents the authentication framework deployed on versions prior to 9.1 SP8. Making this provider Active bypasses the Building Block authentication framework introduced in Blackboard Learn 9.1 SP8, making all other providers in the authentication framework Inactive.
When using the Legacy Authentication Provider, you can manage authentication just as it was managed in release SP7 and earlier, using the bb-config.properties and authentication.properties files.
When upgrading from 9.1 SP7 or earlier to 9.1 SP8, some existing provider types are updated automatically to use the new authentication framework. Migrated providers are the default Learn Internal provider (rdbms) and LDAP. If your Active configured provider is not on the migrated list, it remains Active and functions using the Legacy Authentication Provider.
Blackboard recommends creating new Authentication Providers using the Building Block authentication framework and rewriting any custom authentication modules to use the new framework. If this is not viable, you can use the legacy framework to manage authentication.
Note: The new framework is designed to allow simplified integration of custom authentication, removing the need to deploy custom jar files and manually edit Learn configuration files between upgrades.
Webserver (web delegation) authentication has not been created in the new framework along with other partner authentications such as Datatel. If needed, you can manage these using the Legacy Authentication Provider using the authentication.properties and bb-config.properties files. To learn more, see Authentication Help for Blackboard Learn SP7 and Earlier.