# New Features ## Provide Authentication Context You can now provide additional context to transactions using [Rich Authorization Details](https://docs.stoe.no/bankid-oidc-provider/advanced-topics/authorization-details.md) in [PAR](https://docs.stoe.no/bankid-oidc-provider/api/par.md) requests. --- ## Migration to new BankID Signing service The BankID Server signing and signing using Signdoc over OpenID Connect (OIDC) is being migrated to a new BankID Signing solution. Check out the [migration guide](https://docs.stoe.no/bankid-esign-provider/apis/signdoc/signdoc-migration.md). --- ## Upcoming Data Sharing service > **Warning** > > The `userinfo_endpoint` in the OIDC Discovery configuration will soon be updated to (backwards compatible) The experimental Consent service that provides unverified user data (email, address, phone) through the Userinfo endpoint, is planned to be **discontinued**. The service is being replaced by a new, upcoming Data Sharing service. This impacts you if you use any of the following scopes: - `email` - `address` - `phone` - `nnin` This new Data Sharing service aims to provide **verified**, consented, user data with a modern user experience. The goal is to be **backwards compatible** and still use the Userinfo endpoint to share the data. Note that profile information such as full name and birthdate are available in the ID Token via `profile` scope. If you have legal authority, NNIN will still be available via the `nnin_altsub` scope. `nnin` scope can be used to ask user for consent. The onboarding flow using `nnin` and `id_token_hint` is also discontinued. More information and documentation on migrating to alternative services will be available soon. --- Read about all backwards incompatible API changes in BankID OIDC [here](https://docs.stoe.no/bankid-oidc-provider/api-versions.md).