Managing applications

Applications and APIs in Dataporten Dashboard is either associated with an organization or your personal account. You can select the context by choosing between the available tabs:

Dashboard tabs screenshot

When registering services for production and you are not an administrator for your organization, let your local admin create a placeholder service, and delegate permissions to a developer group.

Personal or organizational context for applications

For applications in production, we strongly recommend that applications is associated with organization accounts, rather than personal accounts. The name and logo of the organization will then be associated with the application and visible to the end user during the login flow..

  • Feide users may register applications and APIs associated with their personal account. This is convenient for experimenting and development. The personal user associated with the application will be visible during the login flow for end users.
  • Guest users need to be associated with a service provider organization to be able to register applications.

All service provider organizations registered in Feide is automatically registered in Dataporten. If you are registered as an administrator in the Feide customer portal, you will be able to login to Dataporten Dashboard with the same credentials.

After logging in to the Dataporten Dashboard you have to:

Registering a new application

Click «Register new application», and you will be prompted to enter some minimal input for you application.

Register new application screenshot

OAuth 2.0 Redirect URL is the URL where the client is redirected back to after authentication. This should be available in the documentation of the software you are about to install. Read more in our technical specification about OAuth and using Dataporten for authentication. The Redirect URI can be changed later.

When submitting the inital form the application is ready to connect to Dataporten, still several additional details can be configured. Take special care to fill in understandable details about your application, including name, description, logo and more. This information will be displayed to end users during login.

OAuth details

In the «OAuth details»-pane you will find all technical details needed that your application would need to configure.

Shreenshot from dashboard showing OAuth and OpenID Connect details

Login providers

Using Dataporten, you probably want to authenticate people using your service. Through Dataporten you can enable several login providers. You - as a service provider - decide which login providers your service should accept.

Which login providers should you enable?

  • When your users are students, researchers, teachers or other employees in Norwegian education: Enable Feide login.
  • If you need to identify and authenticate users outside the education sector (i.e. parents, alumni): Enable ID-porten login.
  • When your users are international students, researchers or teachers/employees: Enable eduGAIN login.
  • If some of your users come from outside of the education sector, and all you need is a way to recognize them and link them to a user account, you should enable guest user login. Dataporten provides several guest user solutions: Twitter, Facebook, LinkedIn and Feide guest users.
  • During development and test phase, you can enable Feide test users. Be sure to disable before moving on to production environment.
  • You need to make sure all your users are able to log in to your service, but you should probably not enable all login providers. That will just make your users confused.

Here you will find more information about the different login providers, how to enable them and when to enable them.

In Dataporten Dashboard you can enable the following login providers for your service:

  • Feide
  • ID-porten
  • International education login, eduGAIN (soon to be added to Dataporten)
  • Social media login
  • Twitter
  • Facebook
  • LinkedIn
  • Feide guest users
  • Feide test users (for test purposes only)

Enabling login providers

When registering your service in the Dataporten Dashboard, you will enable login providers on the page “Login providers”:

Screenshot from dashboard accepting all login providers

If you enable all login providers, this is what your users will see the first time they log in:

Screenshot from login when all login providers are accepted

How to enable Feide login

If your users are students, researchers, teachers or other employees in Norwegian education, you probably want to enable Feide login. In Dashboard, you will enable “Utdanningssektoren”. Be sure not to mix up with “Feide gjestebrukere” or “Feide testbrukere”.

Screenshot from dashboard accepting only Feide login provider

The corresponding end user interface

Screenshot from login when Feide login provider is accepted

If your service should accept logins only from specific schools, you will configure this as well in Dashboard:

Screenshot from dashboard accepting only certain schools

This will allow logins from Tromsø kommune, NTNU and UiB.

Screenshot from login when only some schools are accepted as login providers

How to enable ID-porten login

If your users are people outside of education, i.e. parents or alumni, and you still want a high security level on your logins, you should enable ID-porten login:

Screenshot from dashboard accepting ID-porten as a login provider

More info about how to enable ID-porten (Norwegian only).

How to enable international login through eduGAIN

If your users are international students, researchers, teachers or other employees, you should enable eduGAIN login.

We are working on adding eduGAIN to Dataporten. Ask us for more information by sending an email (

Login through social media

Not all services need to know exactly who the user is and be 100% certain about the user’s identity. These services only need to recognize the user every time he or she logs in to build some kind of user profile for the user.

For these services, login through social media can be a good way to authenticate users. Dataporten offers login through Facebook, LinkedIn and Twitter.

If you enable one or more of these, your users will log in to your service by his/her Twitter, Facebook or LinkedIn account. The user ID received by the service, will be the user ID from Twitter, Facebook or LinkedIn.

You can enable login through all social media:

Screenshot from dashboard accepting social media as login providers

Enable Twitter login

Screenshot from dashboard accepting Twitter as a login provider

Enable Facebook login

Screenshot from dashboard accepting Facebook as a login provider

Enable LinkedIn login

Screenshot from dashboard accepting LinkedIn as a login provider

How to enable login for Feide guest users

For users that don’t have a Feide account, you can enable login through the «Feide guest users solution, also known as OpenIdP.

The «Feide guest users» solution is managed by UNINETT, and is in the process of being phased out. Notice however that the solution will be replaced and users will be alerted before it is removed.

How to enable Feide test users

During the development and test phase, you can enable login for Feide test users. Test usernames and credentials are available through a separate pane on Dashboard for applications that have enabled test accounts.

Screenshot from dashboard enabling test users

Be sure to disable Feide test users before you move your service to a production environment.



Using third-party APIs

Dataporten allows institutions and data owners to make available new datasets that will be very easy to use for application developers.

If you are interested in setting up your own API:

Using the API Gatekeeper

The available APIs can be listed in the tab for third party APIs in the Dataporten Dashboard.

Screenshot from dashboard showing available third-party APIs

APIs that you have made available your self will be visible in the My APIs tab, while all others will be available in the 3rd party API tab.

Some APIs may be made available instantly without moderations, while others may require moderations of either the API owner or each of the institutions behind.