Authentication-levels - Revision history

Regify: /* how to offer authentication */

2019-07-26T07:52:51Z

how to offer authentication

Regify: /* regify supported authentication levels */

2013-02-04T15:30:29Z

regify supported authentication levels

Regify: /* how to offer authentication */

2013-02-04T13:41:09Z

how to offer authentication

Regify at 08:04, 28 March 2012

2012-03-28T08:04:28Z

Regify: Created page with '== regify supported authentication levels == Today, in addition to no authentication, the available levels are 1,3,5,7 and 9. The remaining levels are reserved for future use. T…'

2010-08-05T10:46:48Z

Created page with '== regify supported authentication levels == Today, in addition to no authentication, the available levels are 1,3,5,7 and 9. The remaining levels are reserved for future use. T…'

New page

== regify supported authentication levels ==

Today, in addition to no authentication, the available levels are 1,3,5,7 and 9. The remaining levels are reserved for future use. The levels are defined as follows:

{| class="wikitable" border="1" cellspacing="0" cellpadding="5"
|-
!style="background:#ffdead;"| level
!style="background:#ffdead;" align="left"| description or example
|-
|align="center" |1
| The user contacted the regify-provider verbally by telephone and made his identity credible (social barrier).
|-
|align="center" |3
| The user sent or faxed a copy of his identification card to the regify-provider. In case of an organisation, the user sent a copy of the identification card of the manager or a copy of the business registration / certificate of registration.
|-
|align="center" |5
| - The details of the user are checked against a public directory (eg telephone directory).

- The regify-provider already has an existing, long business relationship with the user.

- The regify-provider personally knows the user.
|-
|align="center" |7
| - The user personally verified his identity to the regify-provider (eg personally showing identification card).

- The user is employed by the regify-provider.
|-
|align="center" |9
| The user has been authenticated by a legally accepted authentication procedure like PostIDENT (germany), Ident.Brief (austria), Die Gelbe Identifikation (switzerland) etc.
|}

@@ Line 49: / Line 49: @@
 == how to offer authentication ==
 As a regify provider, your software already has all functions available to offer customers authentication. But you need to fulfill the following prerequisites:
-* Decide about, what authenticatiojn level you want to offer (see list above).
+* Decide about, what authentication level you want to offer (see list above).
-* Your company's authentication process must get certified by regify S.A.
+* Your company's authentication process must get certified by regify GmbH.
 * You need to support SMS sending (provider option).
 If you have any further questions on authentication or you want to offer, please contact support (AT) regify.com.

@@ Line 4: / Line 4: @@
 {| class="wikitable" border="1" cellspacing="0" cellpadding="5"
 |-
-!style="background:#ffdead;"| level
+| style="border-top:none;border-bottom:1pt solid #000000;border-left:1pt solid #000000;border-right:1pt solid #000000;"| <center>0</center>
-!style="background:#ffdead;" align="left"| description or example
+| colspan="2"  style="border-top:none;border-bottom:1pt solid #000000;border-left:none;border-right:1pt solid #000000;"| User has access to the used email-address. This level is identifying the absence of any further authentication.
 |-
-|align="center" |1
+| style="border-top:none;border-bottom:1pt solid #000000;border-left:1pt solid #000000;border-right:1pt solid #000000;"| <center>1</center>
-| The user contacted the regify-provider verbally by telephone and made his identity credible (social barrier).
+| colspan="2"  style="border-top:none;border-bottom:1pt solid #000000;border-left:none;border-right:1pt solid #000000;"| The user contacted the regify-provider verbally and made his identity credible (social barrier). This can be done by telephone, Skype or other voice systems.
 |-
-|align="center" |3
+| style="border-top:none;border-bottom:1pt solid #000000;border-left:1pt solid #000000;border-right:1pt solid #000000;"| <center>3</center>
-| The user sent or faxed a copy of his identification card to the regify-provider. In case of an organisation, the user sent a copy of the identification card of the manager or a copy of the business registration / certificate of registration.
+| style="border-top:none;border-bottom:1pt solid #000000;border-left:none;border-right:1pt solid #000000;"| The user sent or faxed a copy of his identification card to the regify-provider.
 |-
-|align="center" |5
+| style="border-top:none;border-bottom:1pt solid #000000;border-left:1pt solid #000000;border-right:1pt solid #000000;"| <center>5</center>
-| - The details of the user are checked against a public directory (eg telephone directory).
+| colspan="2"  style="border-top:none;border-bottom:1pt solid #000000;border-left:none;border-right:1pt solid #000000;"| The details of the user or company are checked against a public directory (e.g. call back phone number out of the telephone directory).
-- The regify-provider already has an existing, long business relationship with the user.
+Alternatively, the regify-provider already has an existing, attestable long business relationship with the user or organization.
 |-
-|align="center" |7
+| style="border-top:none;border-bottom:1pt solid #000000;border-left:1pt solid #000000;border-right:1pt solid #000000;"| <center>7</center>
-| - The user personally verified his identity to the regify-provider (eg personally showing identification card).
+| style="border-top:none;border-bottom:1pt solid #000000;border-left:none;border-right:1pt solid #000000;padding-top:0cm;"| The user personally verified his identity to the regify-provider (e.g. personally showing identification card).
 |-
-|align="center" |9
+| style="border-top:none;border-bottom:1pt solid #000000;border-left:1pt solid #000000;border-right:1pt solid #000000;"| <center>9</center>
-| The user has been authenticated by a legally accepted authentication procedure like PostIDENT (germany), Ident.Brief (austria), Die Gelbe Identifikation (switzerland) etc.
+| style="border-top:none;border-bottom:1pt solid #000000;border-left:none;border-right:1pt solid #000000;padding-top:0cm;"| The user has been authenticated by a legally accepted authentication procedure like PostIDENT (Germany), Ident.Brief (Austria), Die Gelbe Identifikation (Switzerland) etc.
 |}
 == how to offer authentication ==

← Older revision		Revision as of 13:41, 4 February 2013
Line 38:		Line 38:
	* You need to support SMS sending (provider option).		* You need to support SMS sending (provider option).

−	If you have any further questions on authentication or you want to offer, please contact support@regify.com.	+	If you have any further questions on authentication or you want to offer, please contact support (AT) regify.com.

← Older revision		Revision as of 08:04, 28 March 2012
Line 29:		Line 29:
	\| The user has been authenticated by a legally accepted authentication procedure like PostIDENT (germany), Ident.Brief (austria), Die Gelbe Identifikation (switzerland) etc.		\| The user has been authenticated by a legally accepted authentication procedure like PostIDENT (germany), Ident.Brief (austria), Die Gelbe Identifikation (switzerland) etc.
	\|}		\|}
		+
		+
		+
		+	== how to offer authentication ==
		+	As a regify provider, your software already has all functions available to offer customers authentication. But you need to fulfill the following prerequisites:
		+	* Decide about, what authenticatiojn level you want to offer (see list above).
		+	* Your company's authentication process must get certified by regify S.A.
		+	* You need to support SMS sending (provider option).
		+
		+	If you have any further questions on authentication or you want to offer, please contact support@regify.com.