The new authenticate() call now allows for a custom authentication provider implementation to support a scheme where the identity of the authenticated resource is embedded in the credentials; for example, a web API where the authenticated API caller is identified via an encrypted token in an HTTP header.
…eter alone (i.e. no resource parameter)
The new authenticate() call now allows for a custom authentication provider implementation to support a scheme where the identity of the authenticated resource is embedded in the credentials; for example, a web API where the authenticated API caller is identified via an encrypted token in an HTTP header.