BankID (NO)

Used by around 4 million Norwegians, BankID has become a household brand and a highly trusted digital identification service for Norwegian citizens.​

Enabl​​e BankID in your services

To get you started with BankID identification through E-Ident, Nets will need a merchant certificate and some configuration setting information from you. The configuration settings are supplied in the setup dialogue with support. 

More information about BankID:

Merchant certificate

​​​​​Nets through the Signing and Identification Services are resellers of BankID merchant certificates, and this can be ordered either separately or together with E-Ident and/or E-Signing. When ordering a merchant certificate through Nets, you will receive an information letter asking you to complete a form with information needed to create a BankID “brukerstedsavtale” with BankID Norge. ​Note: In this form you need to ​specify if you are allowed to handle SSN. 

The form shall be returned to our support and based on the form Nets will register this order at BankID. After the registration you will be asked to confirm and sign the order. When the order is signed with BankID Norge, it will be sent to your bank for processing. Your bank may use up to 10 business days for processing the order. Nets will  then recei​ve activation information for your BankID merchant certificate from your bank. The merchant certificate will be activated and connected to your configuration.​

In cases where you use another reseller, the BankID activation link and code must be sent to Nets without activating it. Contact Nets support to get contact details of recei​​​ver of the link and code. 

Test merchant certificate

Nets will set you up with a common test merchant certificate if nothing else have been agreed. ​

Test users

​​​Test users are available here.

To get notified about BankID issues in BankID preproduction environment, subscribe to updates at this page:

Information about the end user

​Type​OIDC​SAML​Comments
​Birth date birthdate​

Requires scope=profile

DOBEnd user's date of birth.
​End user certificate

certificate

Requires scope=cert

CERTIFICATE​The end user's certificate.
​Certificate policy OID

certpolicyoid

Requires scope=cert

CERTPOLICYOID​The certificate policy OID from the end user certificate.
​Common name

cn

Requires scope=cert

​CN​The common name from the end user's certificate. Example: "Olsen, Ole"
Distinguished name

dn​

Requires scope=cert

DN​​The distinguished name from the end user's certificate. Example: "CN=Olsen\\, Ole,O=TestBank1 AS,C=NO,SERIALNUMBER=xxxx-xxxx-x-xxxxxx"
​Family name

family_name

Requires scope=profile

SURNAMEEnd user's family name. ​Deducted from the first part of the CN field of the BankID end user certificate. Example "Olsen".
​Given name

given_name

Requires scope=profile

GIVENNAMEEnd user's first name(s). ​​Deducted from the last part of the CN field of the BankID end user certificate. Example "Ole".
Personal identifier

​no_bid_pid / pid

Requires scope=openid

​NO_BID_PID​​Norwegian BankID personal identifier. For the OIDC protocol, this is returned in both the no_bid_pid and pid claim.
​Norwegian SSN

​no_ssn / ssn

Requires scope=ssn

​NO_SSN

​The end user's social security number (no: fødselsnummer). For the OIDC protocol, this is returned in both the no_ssn and ssn claim.  

Handling of SSN

​​All companies that are allowed to handle social security numbers (SSN) can get this in return after a BankID identification. For customers using the SAML protocol, SSN is returned as default, but this can be turned off by appending returnssn=false to the identification request. For customers using OIDC, SSN will only be returned if scope=ssn is set in the identification request. Read more about the optional eID specific scopes and identification request parameters for OIDC and SAML respectively.

Note: Remember to specify that you want to process SSN when ordering your BankID merchant certificate and giving Nets your E-Ident configuration details.

​​User experience​

BankID client

Step 1 (enter SSN):

BankIDNO - step 1_uten.png 

Step 2 (enter OTP):​

BankIDNO - step 2_uten.png

​Step 3 (enter password):

BankIDNO - step 3_uten.png  

​IFRAME sizes

The recommended and minimum IFRAME sizes from BankID are:

  • Large screen (Desktop/tablet): 396px (w) by 280px (h) (recommended) / 370px (w) by 204px (h) (minimum)
  • Small screen (Smartphone) (only minimum sizes): 320px (w) by 350px (h) (portrait) / 480px (w) by 200px (h) (landscape)

CSS file adjustment

The BankID client should be styled with CSS to display properly. The default styling has CSS rule that set the proper sizes. Styling can be overridden either by setting av style URL in the customer configuration at Nets or by sending a style parameter when starting the identification. The default CSS styling sets width and height to 100%. The client will then expand to fill the container (iframe), regardless of the container size.

When overriding styling, the sample CSS below will produce the same effect as the default styling.

#nobankid_index_html {
    height: 100%;
    overflow-y: hidden; /* make sure no scroll bar is shown */
}
#nobankid_index_html .iframe,
#nobankid_index_html .iframe .ipage {
    height: 100%;
}
#nobankid_index_html .iframe .ipage .main {
    height: 100%;
    min-height: 200px;
}

​​Read more about CSS styling and download E-Ident default style here.​​​

​Error codes​

BankID specific error codes can be found in BankID documentation at https://confluence.bankidnorge.no/confluence/kiev-open/bankid-services-error-codes

 

BankID logo

If needed, the BankID logo can be downloaded from https://brand.vipps.no/d/DgLepABXUPY4/bankid.