Search results

Jump to: navigation, search

Page title matches

  • ...h Swivel versions up to and including 3.7. For later versions see [[Mobile Phone Client]]. ...Mobile Phone Client'', the Swivlet referring explicitly to the Java Mobile Phone Client.
    10 KB (1,427 words) - 12:52, 11 May 2017
  • = Mobile Phone Client 2.x = ...le Phone Client 2.0'', the Swivlet referring explicitly to the Java Mobile Phone Client
    3 KB (480 words) - 12:52, 11 May 2017
  • Mobile Phone Clients require the access device to use PAP authentication to provide a mo PINsafe Mobile Phone Client or Swivlet
    929 bytes (137 words) - 19:35, 15 January 2019
  • Swivel 3.8 introduced the ability to reformat a mobile phone number from a data source such as Active Directory, for a user. ...sed, then it may not add/remove the prefix. Test with the Swivel attribute phone, which can be mapped to different LDAP attributes. This affects versions up
    665 bytes (99 words) - 12:52, 11 May 2017
  • = The Swivel Windows Phone 8 2.0 App Overview = ...to download, configure and use this client. For other phones see [[Mobile Phone Client]] for earlier versions.
    10 KB (1,657 words) - 12:52, 11 May 2017
  • ...op up from the Swivel server resets all the security strings on the mobile phone. You can use the device to get one-time codes for Swivel login and PIN chan This application is for phones running Windows Phone 7.x only
    9 KB (1,383 words) - 12:52, 11 May 2017

Page text matches

  • ...to download, configure and use this client. For other phones see [[Mobile Phone Client]]. The Swivel virtual or hardware appliance must be reachable from the mobile phone to receive a [[Security string]]
    11 KB (1,667 words) - 12:52, 11 May 2017
  • ...sport\Attributes, this is usually mail for SMTP and mobile for SMS by Cell Phone. ...ve the correct information for transport, i.e. an email address and mobile phone number. It is recommended to test with a small number of users first to ens
    28 KB (4,481 words) - 12:52, 11 May 2017
  • Add new users, set user details (eg mobile phone number), synchronise a repository, delete users
    5 KB (643 words) - 23:50, 2 January 2019
  • Mobile Phone on which to receive SMS text messages ...number of security strings to be sent. Ensure that the transport attribute phone is selected.
    5 KB (840 words) - 12:52, 11 May 2017
  • Phone on which to receive Voice calls. ...number of security strings to be sent. Ensure that the transport attribute phone is selected.
    4 KB (683 words) - 12:52, 11 May 2017
  • Q). What would happen if the user mobile phone number is added later to the user in Active Directory?
    5 KB (954 words) - 12:52, 11 May 2017
  • ...es for the user. These can be used as message destinations (e.g. email and phone), alternative identifiers when logging in, for searching the user list, or <Attribute name="phone" value="447817360285"/>
    16 KB (2,315 words) - 16:15, 1 March 2023
  • *Security String for login (optional), by SMS, email, mobile phone client
    2 KB (324 words) - 12:52, 11 May 2017
  • * When making a login with [[SMS]], [[Token]], [[Mobile Phone Client]], do not click on Start Session to generate an image as the login p
    4 KB (568 words) - 12:52, 11 May 2017
  • Add new users, set user details (eg mobile phone number), synchronise a repository, delete users
    9 KB (1,302 words) - 12:48, 19 May 2023
  • Android Phone The Swivel virtual or hardware appliance must be reachable from the mobile phone to receive security strings
    13 KB (2,020 words) - 12:52, 11 May 2017
  • ...to download, configure and use this client. For other phones see [[Mobile Phone Client]] for earlier versions. The Swivel virtual or hardware appliance must be reachable from the mobile phone to receive security strings
    9 KB (1,365 words) - 12:52, 11 May 2017
  • ...el can provide Two Factor authentication with [[SMS]], [[Token]], [[Mobile Phone Client]] and strong Single Channel Authentication [[TURing]], [[Pinpad]] or ...hould be possible to authenticate by [[SMS]], hardware [[Token]], [[Mobile Phone Client]] and [[Taskbar How to Guide | Taskbar]] to verify that the RADIUS a
    4 KB (565 words) - 12:52, 11 May 2017
  • [[Mobile Phone Client]]
    931 bytes (125 words) - 12:52, 11 May 2017
  • ...hould be possible to authenticate by [[SMS]], hardware [[Token]], [[Mobile Phone Client]] and [[Taskbar How to Guide | Taskbar]] to verify that the RADIUS a
    20 KB (2,940 words) - 13:58, 19 May 2017
  • ...el can provide Two Factor authentication with [[SMS]], [[Token]], [[Mobile Phone Client]] and strong Single Channel Authentication [[TURing]], [[Pinpad]] or ...hould be possible to authenticate by [[SMS]], hardware [[Token]], [[Mobile Phone Client]] and [[Taskbar How to Guide | Taskbar]] to verify that the RADIUS a
    8 KB (1,205 words) - 12:52, 11 May 2017
  • The Swivel Mobile Phone Client allows 99 security strings or One Time Codes for PINless authenticat There are two versions of the Blackberry Mobile Phone client one for Versions 3.8 and later and one for earlier versions.
    10 KB (1,551 words) - 12:52, 11 May 2017
  • ...to download, configure and use this client. For other phones see [[Mobile Phone Client]] for earlier versions. The Swivel virtual or hardware appliance must be reachable from the mobile phone to receive security strings
    10 KB (1,515 words) - 12:52, 11 May 2017
  • ...el can provide Two Factor authentication with [[SMS]], [[Token]], [[Mobile Phone Client]], It is not currently possible to embed the [[TURing]] or [[Pinpad] ...hould be possible to authenticate by [[SMS]], hardware [[Token]], [[Mobile Phone Client]] and [[Taskbar How to Guide | Taskbar]] to verify that the RADIUS a
    3 KB (495 words) - 12:52, 11 May 2017
  • Mobile Phone on which to receive SMS text messages ...number of security strings to be sent. Ensure that the transport attribute phone is selected.
    4 KB (538 words) - 12:52, 11 May 2017
  • *PINsafe mobile phone apps allow the user to generate security strings to change their PIN. Security strings can be used from SMS text messages and Mobile Phone Clients to change the PIN. Where the single channel graphical image is not
    25 KB (3,787 words) - 12:52, 11 May 2017
  • ...vlet), Windows Mobile users can use the changePIN directly on their mobile Phone. ...Image Request but is not a member of the correct group. Use SMS or Mobile Phone security strings to changePIN.
    4 KB (591 words) - 12:52, 11 May 2017
  • ...hould be possible to authenticate by [[SMS]], hardware [[Token]], [[Mobile Phone Client]] and [[Taskbar How to Guide | Taskbar]] to verify that the RADIUS a
    7 KB (1,159 words) - 12:52, 11 May 2017
  • ...hould be possible to authenticate by [[SMS]], hardware [[Token]], [[Mobile Phone Client]] and [[Taskbar How to Guide | Taskbar]] to verify that the RADIUS a
    5 KB (793 words) - 12:52, 11 May 2017
  • Swivel users can use Swivel’s [[Token]], [[SMS]], [[Mobile Phone Client]], as well as the single channel [[TURing]] and [[Pinpad]] methods t ...dy for two factor authentication using standard SMS delivery or the Mobile Phone Client.
    10 KB (1,518 words) - 12:52, 11 May 2017
  • ...el can provide Two Factor authentication with [[SMS]], [[Token]], [[Mobile Phone Client]] and strong Single Channel Authentication [[TURing]], [[Pinpad]] or ...ne. This script can be used for [[TURing]], [[SMS]], [[Token]] or [[Mobile Phone Client]]. There is an alternative customisation for [[Pinpad]], available f
    18 KB (2,746 words) - 12:52, 11 May 2017
  • *[[Mobile Phone Client]] |Product || SMS Text || SMS On Demand || [[Mobile Phone Client]] || [[Token]] || [[Taskbar How to Guide | Taskbar Utility]] || [[Si
    7 KB (1,105 words) - 08:54, 30 August 2019
  • *[[Mobile Phone Client]]
    4 KB (572 words) - 12:52, 11 May 2017
  • ...PINsafe as the authentication server for authentication using SMS, Mobile Phone Client or the PINsafe [[Taskbar How to Guide | Taskbar ]] utility.
    2 KB (260 words) - 12:52, 11 May 2017
  • * Mobile Phone Client
    700 bytes (94 words) - 12:52, 11 May 2017
  • ...hould be possible to authenticate by [[SMS]], hardware [[Token]], [[Mobile Phone Client]] and [[Taskbar How to Guide | Taskbar]] to verify that the RADIUS a For SMS or Mobile Phone Apps do not click on the Get Image button, but enter the OTC
    17 KB (2,707 words) - 12:52, 11 May 2017
  • For SMS or Mobile Phone Apps do not click on the Get Image button, but enter the OTC
    15 KB (2,404 words) - 12:52, 11 May 2017
  • ...ition. The standard edition allows authentication using SMS, Email, Mobile Phone applet, PINsafe [[Taskbar How to Guide | Taskbar]], but does not allow the
    1 KB (178 words) - 12:52, 11 May 2017
  • ...ition. The standard edition allows authentication using SMS, Email, Mobile Phone applet, Swivel [[Taskbar How to Guide | Taskbar]], but does not allow the s ...login page and enter username, AD Password and OTC from the SMS or Mobile Phone Client. Check the PINsafe logs to ensure that a RADIUS request has been see
    2 KB (335 words) - 12:52, 11 May 2017
  • ...el can provide Two Factor authentication with [[SMS]], [[Token]], [[Mobile Phone Client]] and strong Single Channel Authentication [[TURing]], [[Pinpad]] or For SMS or Mobile Phone Apps do not click on the Get Image button, but enter the OTC
    24 KB (3,662 words) - 12:52, 11 May 2017
  • ...an provide Two Factor authentication with [[SMS]], [[Token]], and [[Mobile Phone Client]] and strong Single Channel Authentication with [[TURing]] or [[Pinp
    29 KB (4,393 words) - 15:04, 20 August 2019
  • |Product || SMS Text || [[Mobile Phone Client]] || [[Taskbar How to Guide | Taskbar Utility]] || [[Single Channel
    2 KB (278 words) - 12:52, 11 May 2017
  • ...ce using some of the PINsafe authentication mechanisms such as SMS, mobile Phone applet, and [[Taskbar How to Guide | Taskbar]]. Additional configuration op
    15 KB (2,312 words) - 12:52, 11 May 2017
  • Mobile Phone on which to receive SMS text messages '''Destination attribute:''' Default: phone, the attributes that is read from the data source to determine a users tele
    5 KB (790 words) - 12:52, 11 May 2017
  • ...PINsafe as the authentication server for authentication using SMS, Mobile Phone Client or the PINsafe [[Taskbar How to Guide | Taskbar ]] utility. It is no ...hould be possible to authenticate by [[SMS]], hardware [[Token]], [[Mobile Phone Client]] and [[Taskbar How to Guide | Taskbar]] to verify that the RADIUS a
    6 KB (948 words) - 12:52, 11 May 2017
  • * A - Destination (e.g. email address or phone number) Auxiliary information on users, such as email address, mobile phone number, alternative usernames.
    10 KB (1,522 words) - 09:15, 31 May 2022
  • ...nce, the DELL engineer can provide some hardware diagnostic steps over the phone, which can assist in locating the fault.
    2 KB (275 words) - 12:52, 11 May 2017
  • Mobile Phone for SMS Enter the mobile phone number including country code without a + or 00
    744 bytes (108 words) - 12:52, 11 May 2017
  • 1. Authentication details are sent by [[SMS]]/Phone Call across the mobile phone network.
    2 KB (290 words) - 12:52, 11 May 2017
  • ...have enough credit to send an SMS and new credits must be purchased or the phone number is incorrect and the message cannot be sent. ...has been seen with an incorrectly configured DNS entry in the Java Mobile Phone client
    69 KB (10,673 words) - 08:45, 6 September 2017
  • ...hould be possible to authenticate by [[SMS]], hardware [[Token]], [[Mobile Phone Client]] and [[Taskbar How to Guide | Taskbar]] to verify that the RADIUS a
    12 KB (1,552 words) - 14:43, 1 June 2018
  • ...hould be possible to authenticate by [[SMS]], hardware [[Token]], [[Mobile Phone Client]] and [[Taskbar How to Guide | Taskbar]] to verify that the RADIUS a
    11 KB (1,661 words) - 12:52, 11 May 2017
  • ...hould be possible to authenticate by [[SMS]], hardware [[Token]], [[Mobile Phone Client]] and [[Taskbar How to Guide | Taskbar]] to verify that the RADIUS a
    4 KB (672 words) - 12:52, 11 May 2017
  • ...hould be possible to authenticate by [[SMS]], hardware [[Token]], [[Mobile Phone Client]] and [[Taskbar How to Guide | Taskbar]] to verify that the RADIUS a
    7 KB (1,046 words) - 13:30, 14 August 2018
  • ...to be redirected to a help desk in case anyone tries to contact the source phone number for support. Nokia Mobile Phone connected by data cable
    11 KB (1,718 words) - 11:02, 9 April 2021
  • ...image, Dual Channel Confirmation, Security String Index number, and mobile phone applications are requested from the client to the Swivel server (although u
    2 KB (308 words) - 12:52, 11 May 2017
  • '''AD''' – Active Directory, windows user management system, similar to a phone book. ...ight Directory Access Protocol – contains user information, similar to a phone book.
    9 KB (1,339 words) - 12:52, 11 May 2017
  • ...el can provide Two Factor authentication with [[SMS]], [[Token]], [[Mobile Phone Client]] and strong Single Channel Authentication [[TURing]], [[Pinpad]] or
    12 KB (1,833 words) - 08:35, 19 May 2017
  • ...configured to allow authentication for Dual channel such as SMS and mobile phone applet. To configure additional options such as the graphical single channe ...old and new one time codes are entered. A user may use SMS or tthe mobile phone to change their PIN. If a PINsafe password is being used, they must use <pa
    7 KB (1,064 words) - 12:52, 11 May 2017
  • <value>phone</value>
    7 KB (956 words) - 15:41, 9 July 2018
  • == Provision a mobile Phone Client == To provision or reprovision a mobile phone client user, select the user and click on Quick Reprovision. This will send
    12 KB (1,945 words) - 12:52, 11 May 2017
  • ...to download, configure and use this client. For other phones see [[Mobile Phone Client]]. The Swivel virtual or hardware appliance must be reachable from the mobile phone to receive security strings
    10 KB (1,515 words) - 12:52, 11 May 2017
  • ...to download, configure and use this client. For other phones see [[Mobile Phone Client]] for earlier versions. The Swivel virtual or hardware appliance must be reachable from the mobile phone to receive security strings
    11 KB (1,682 words) - 12:52, 11 May 2017
  • Mobile Phone on which to receive SMS text messages ...number of security strings to be sent. Ensure that the transport attribute phone is selected.
    3 KB (465 words) - 12:52, 11 May 2017
  • Username,username,first-name,last-name,email,disabled,phone Username,username,first-name,last-name,email,disabled,phone,group_1,group_2
    4 KB (684 words) - 11:11, 10 January 2019
  • Mobile Phone on which to receive SMS text messages The mobile phone number is expected to use country code: <countrycode><telephonenumber>
    3 KB (477 words) - 12:52, 11 May 2017
  • ...e to integrate a graphical image, but I could get my OTP via SMS or mobile phone client?
    6 KB (1,081 words) - 12:52, 11 May 2017
  • ...h Swivel versions up to and including 3.7. For later versions see [[Mobile Phone Client]]. ...Mobile Phone Client'', the Swivlet referring explicitly to the Java Mobile Phone Client.
    10 KB (1,427 words) - 12:52, 11 May 2017
  • ...el can provide Two Factor authentication with [[SMS]], [[Token]], [[Mobile Phone Client]] and strong Single Channel Authentication [[TURing]], [[Pinpad]] or
    19 KB (2,911 words) - 14:07, 18 May 2017
  • ...el can provide Two Factor authentication with [[SMS]], [[Token]], [[Mobile Phone Client]] and strong Single Channel Authentication [[TURing]], [[Pinpad]] or
    19 KB (2,953 words) - 08:04, 14 July 2020
  • '''Reformat Phone Number: ''' If this option is set to Yes, then any phone number imported from the repository is reformatted by removing all non-digi '''Prefix to remove: ''' If Reformat Phone Number is enabled and this option is not empty, then the first occurrence o
    9 KB (1,578 words) - 12:52, 11 May 2017
  • '''Destination Attribute:''' Ensure this is set to phone
    7 KB (1,084 words) - 12:52, 11 May 2017
  • ...e internal resources using Dual channel authentication such as SMS, Mobile Phone Client and the Taskbar utility [[Taskbar_How_to_Guide | Taskbar How to Guid
    6 KB (803 words) - 12:52, 11 May 2017
  • ...nel Dual Channel] authentication using SMS, [[Mobile_Phone_Client | Mobile Phone Clients]] and [[Single_Channel_How_To_Guide | Single Channel]] using TURing
    30 KB (4,745 words) - 12:52, 11 May 2017
  • ...rates a OTC for which they want the new PIN to be. Dual channel and mobile Phone Clients may be used with the ChangePIN as well as the TURing image. ChangePIN using dual channel or mobile phone client
    15 KB (2,169 words) - 12:52, 11 May 2017
  • This document supplements the existing documents for individual phone types. ...s Yes/No, Default No. Version 3.9.6 onwards. This option allows the Mobile Phone App user to browse through the security strings. Availability to this featu
    2 KB (267 words) - 12:52, 11 May 2017
  • This document supplements the existing documents for individual phone types. '''Support Phone Number:''' Option text, Default empty. If a phone number is set, the user will be shown an option under the help section to c
    2 KB (393 words) - 08:33, 19 May 2017
  • = Mobile Phone Client 2.x = ...le Phone Client 2.0'', the Swivlet referring explicitly to the Java Mobile Phone Client
    3 KB (480 words) - 12:52, 11 May 2017
  • Mobile Phone Clients require the access device to use PAP authentication to provide a mo PINsafe Mobile Phone Client or Swivlet
    929 bytes (137 words) - 19:35, 15 January 2019
  • This document supplements the existing documents for individual phone types. Supported [https://kb.swivelsecure.com/wiki/index.php/Category:Phone Mobile device]
    7 KB (971 words) - 12:52, 11 May 2017
  • = How to Provision a Swivel Mobile Phone Client= A user guide to provision a Swivel Mobile Phone Client to provide authentication One Time Codes and Security strings.
    3 KB (454 words) - 14:26, 18 April 2018
  • A Mobile Phone user may request a Mobile Provision Code to allow their Mobile Phone Client to download security strings. The Swivel Helpdesk or Administrator c ...ument outlines how to configure the reset.war utility that provides Mobile Phone Provision and Re-Provision. Use of the [[User Portal]] should be considered
    5 KB (653 words) - 12:52, 11 May 2017
  • ...Swivel mobile phone apps allow security strings and One Time Codes on the phone to be used for authentication. More recent versions of the apps, using '''A Mobile Phone App enabled user
    1 KB (230 words) - 12:52, 11 May 2017
  • The Mobile Phone Client (Swivlet) may fail to authenticate a user for a number of reasons. T Mobile Phone Client or Swivlet
    881 bytes (131 words) - 12:52, 11 May 2017
  • ...y Strings or 10 security strings across 2 SMS messages. Usually the mobile phone reassembles SMS messages into one message.
    5 KB (712 words) - 12:52, 11 May 2017
  • Mobile Phone on which to receive SMS text messages '''Destination attribute:''' phone
    4 KB (704 words) - 12:52, 11 May 2017
  • Ensure the data source attribute is correct, i.e. mobile for AD, phone for LDAP and XML, see [[Transport Attribute]]
    821 bytes (130 words) - 12:52, 11 May 2017
  • Ensure the data source attribute is correct, i.e. mobile for AD, phone for LDAP and XML, see [[Transport Attribute]]
    821 bytes (130 words) - 12:52, 11 May 2017
  • Mobile Phone on which to receive SMS text messages ...number of security strings to be sent. Ensure that the transport attribute phone is selected.
    4 KB (539 words) - 12:52, 11 May 2017
  • *Pressing # or other defined characters on phone keypad [[OneTouch Mobile]] using the Swivel [[Mobile Phone Client]]
    2 KB (367 words) - 12:52, 11 May 2017
  • Swivel [[Mobile Phone Client]] Version 2.1.2 for One Touch Mobile client based solution. Swivel [[Mobile Phone Client]] must be configured to obtain its details from the Swivel [[SSD]].
    7 KB (1,135 words) - 12:52, 11 May 2017
  • *Entering the OTC comes only on the phone ...Transports How To Guide]] and [[OneTouch Mobile]] uing the Swivel [[Mobile Phone Client]]
    6 KB (986 words) - 12:52, 11 May 2017
  • *[[Mobile Phone Client]] application
    820 bytes (128 words) - 12:52, 11 May 2017
  • ...N authentication with a Username and One Time Code (OTC) using SMS, mobile phone clients, and the [[Taskbar How to Guide | Taskbar]]. The Single Channel TUR
    3 KB (458 words) - 12:52, 11 May 2017
  • ...el can provide Two Factor authentication with [[SMS]], [[Token]], [[Mobile Phone Client]] and strong Single Channel Authentication [[TURing]], [[Pinpad]] or
    16 KB (2,325 words) - 10:16, 18 May 2017
  • Q). Do I need a phone number? Q). Do I need an email or phone number?
    2 KB (459 words) - 12:52, 11 May 2017
  • == The Security String as a Mobile Phone Message == The security string can be sent by text message to a mobile phone.
    1 KB (249 words) - 12:52, 11 May 2017
  • Mobile Phone on which to receive SMS text messages ...number of security strings to be sent. Ensure that the transport attribute phone is selected.
    3 KB (377 words) - 12:52, 11 May 2017
  • ...l with Swivel as the authentication server using RADIUS with SMS, [[Mobile Phone Client]], and [[ Taskbar How to Guide | Taskbar Authentication]]. The solut
    5 KB (719 words) - 12:52, 11 May 2017
  • Swivel 3.8 introduced the ability to reformat a mobile phone number from a data source such as Active Directory, for a user. ...sed, then it may not add/remove the prefix. Test with the Swivel attribute phone, which can be mapped to different LDAP attributes. This affects versions up
    665 bytes (99 words) - 12:52, 11 May 2017
  • ...eID authentication before security strings can be downloaded by the mobile phone application see [[IPhone]], [[Swivlet_How_To_Guide|Swivlet Java Applet]], [ The current PINsafe PositiveID will not function with the Swivlet/Mobile Phone Client.
    16 KB (2,390 words) - 08:34, 19 May 2017
  • If you have received text message on your mobile phone with multiple security strings, you use, each in turn, if you do not know w
    2 KB (250 words) - 12:52, 11 May 2017
  • For the Mobile Phone Provision administration guide see: and [[Mobile Re-Provision How to Guide [[Mobile Phone Client]] Users can request a [[Mobile Provision Code]] using the [[User Por
    4 KB (685 words) - 12:52, 11 May 2017
  • *[[Mobile Phone Client]] provisioning, security strings and One Time Codes ...nce build 2.0.12 have the old proxy and need to be upgraded for the Mobile Phone Provisioning.
    2 KB (248 words) - 12:52, 11 May 2017
  • Mobile Phone Client 2.1.1 onwards Mobile Phone/tablet with camera
    3 KB (415 words) - 12:52, 11 May 2017
  • ...channels that provide multiple security strings (i.e. Dual Channel, Mobile Phone Client or Swivlet/Swivlet.Net/iPhone app) with RADIUS protocols other than
    948 bytes (141 words) - 13:17, 10 September 2020
  • ...One Time Code from the security string (Single Channel, SMS, SMTP, Mobile Phone applet)
    4 KB (559 words) - 12:52, 11 May 2017
  • Note for access using mobile phone devices (Swivlet, Mobile Phone apps such as .NET mobile, iPhone App the access device must be configured t
    2 KB (287 words) - 07:47, 8 June 2020
  • Q). I am using RADIUS with the Mobile Phone Client or Swivlet/Dual Channel. Why is authentication failing?
    952 bytes (177 words) - 12:52, 11 May 2017
  • ...ests the password for the user and authenticates itself. Also see [[Mobile Phone Client RADIUS Authentication]] ...dable consequence of the way most RADIUS protocols work. Also see [[Mobile Phone Client RADIUS Authentication]]
    16 KB (2,447 words) - 17:45, 12 December 2017
  • ...ity strings include Dual Channel (if the number of strings is > 1), Mobile Phone Client, Swivlet, Swivel.Net (Swivlet for Windows Mobile) and PINsafe iClien
    1 KB (228 words) - 12:52, 11 May 2017
  • '''destination:''' the transport destination (email address or phone number) The transport destination (email address or phone number)
    2 KB (286 words) - 12:52, 11 May 2017
  • Phone Number <header>Phone</header>
    38 KB (5,834 words) - 14:43, 14 September 2022
  • ...er their username and click on request code. They are sent to their mobile phone a request code which they enter into the web page. If this is correctly ent
    10 KB (1,466 words) - 12:52, 11 May 2017
  • The PIN is only sent to the users defined transport, such as a mobile phone or email address.
    2 KB (335 words) - 12:52, 11 May 2017
  • ...nd sync again. This will recreate the user so [[Dual Channel]] ad [[Mobile Phone Client]] strings are reset and their [[Token]] unallocated.
    2 KB (317 words) - 12:52, 11 May 2017
  • The user does not have a transport defined (i.e. a phone number or email address), or the [[Transport Attribute]] has not been defin
    3 KB (544 words) - 12:52, 11 May 2017
  • '''Destination attribute:''' phone
    3 KB (381 words) - 12:52, 11 May 2017
  • ...e to send users a One Time Code (OTC) for authentication, using the mobile phone as a device for two factor authentication. Swivel supports the following: As an alternative to SMS text messaging see [[Mobile Phone Client]]. For alternative authentication see [[Authentication Methods]].
    3 KB (423 words) - 12:52, 11 May 2017
  • Does the user have a valid mobile phone == Mobile/Cell Phone issues ==
    3 KB (440 words) - 12:52, 11 May 2017
  • * Phone : the user's mobile phone number. ...the fields are entered as described above, except see below for email and phone.
    8 KB (1,270 words) - 12:52, 11 May 2017
  • Swivel Mobile Phone Client with Server ID option. ...h can be sent to users to automatically enter these fields on their Mobile Phone Client.
    5 KB (797 words) - 15:43, 27 October 2017
  • ...anged. Up to version 3.6, this means that either the transport name or the phone number has changed. In 3.7, it only resends if the number has changed. In 3
    1 KB (153 words) - 12:52, 11 May 2017
  • *[[Mobile Phone Client]] application
    1 KB (190 words) - 12:52, 11 May 2017
  • [[Mobile Phone Client RADIUS Authentication]]
    2 KB (250 words) - 12:52, 11 May 2017
  • ...can provide Two Factor authentication such as [[SMS]], [[Token]], [[Mobile Phone Client]] and strong Single Channel Authentication [[TURing]], [[Pinpad]] or
    7 KB (1,102 words) - 12:52, 11 May 2017
  • ...prompted for a One Time Code, either from a graphical TURing image, mobile phone client or a Challenge and Response SMS sent to the user.
    7 KB (984 words) - 12:52, 11 May 2017
  • '''destination:''' The transport value, e.g. email address or phone number. '''destination:''' The transport value, e.g. email address or phone number.
    5 KB (801 words) - 09:24, 19 July 2018
  • Using SMS turns the users mobile phone into a token for authentication, and has become an accepted form of two fac Existing technology for reading the text message can be employed by mobile phone users. In addition some SMS providers support text to voice so the user wou
    9 KB (1,376 words) - 12:52, 11 May 2017
  • *[[Mobile Phone Client | Mobile Phone Clients]]
    5 KB (846 words) - 12:52, 11 May 2017
  • |Phone|||| |Secondary Phone||||
    5 KB (687 words) - 12:52, 11 May 2017
  • [[Phone Number Format incorrect]]
    3 KB (399 words) - 12:52, 11 May 2017
  • Mobile Phone on which to receive SMS text messages ...number of security strings to be sent. Ensure that the transport attribute phone is selected.
    3 KB (465 words) - 12:52, 11 May 2017
  • If you have received text message on your mobile phone with multiple security strings, you use, each in turn, if you do not know w
    1 KB (237 words) - 12:52, 11 May 2017
  • *Pressing # or other defined characters on phone keypad *Enter [[OTC]] on phone keypad. The OTC may be from a security string or [[PINless How To Guide | P
    6 KB (854 words) - 12:52, 11 May 2017
  • | XML || email || phone | LDAP || email || phone
    2 KB (269 words) - 12:52, 11 May 2017
  • Users can send security strings by dual channel, single channel and mobile phone client, and one dual channel transport for [[User Alerts]]. PINsafe can wor [[Mobile Phone Client]]
    12 KB (1,770 words) - 09:53, 13 February 2020
  • *[[Mobile Phone Client]] ...out PIN extraction, see [[PINless How To Guide]]. Possession of the mobile phone acts as a '''Something you have''' for [[Two Factor Authentication]].
    6 KB (913 words) - 14:06, 18 May 2017
  • *Something you have (e.g. [[Mobile Phone Client | Mobile Phone]], Hardware [[Token]])
    568 bytes (82 words) - 05:32, 25 August 2017
  • ...rovision''' Send a device provision code to the user to provision a mobile phone client, see [[Mobile Provision Code]]
    4 KB (663 words) - 12:52, 11 May 2017
  • * Transport destinations (e.g. email address, phone number) | phone || phone || phone || mobile || mobile
    9 KB (1,411 words) - 16:12, 27 February 2019
  • ...allows a user to provision their [[Mobile_Phone_Client_How_To_Guide|Mobile Phone]] for authentication.
    10 KB (1,578 words) - 12:52, 11 May 2017
  • Ensure the data source attribute is correct, i.e. mobile for AD, phone for LDAP and XML. See [[Transport Attribute]] If some users do not have a transport (i.e. mobile phone number or email address), then consider creating a separate group for them
    2 KB (269 words) - 12:52, 11 May 2017
  • Does the user have a valid security string (sinlge, dual, Mobile Phone Client or swivlet)?
    3 KB (485 words) - 12:52, 11 May 2017
  • ....1. using RADIUS authentication protocol with [[SMS]], [[Token]], [[Mobile Phone Client]], and [[ Taskbar How to Guide | Taskbar Authentication]] The VMware View Client also functions on a number of mobile phone client devices including iPhone, iPad and Android.
    6 KB (864 words) - 12:52, 11 May 2017
  • ...ng]], [[Pinpad | PINpad]]) and Pinless for dual channel ([[SMS]], [[Mobile Phone Client]]) *Alpanumeric strings can be used for TURing, SMS and Mobile Phone Apps and still allow the numeric PINpad to still function
    60 KB (8,810 words) - 10:10, 2 May 2024
  • '''Token''' Shows the token/mobile Phone Client security expected any string index where multiple security strings a * Use mobile Phone Client where no SMS is being received
    4 KB (560 words) - 14:52, 16 August 2018
  • The one time code can be sent by an SMS message or a mobile phone client. Do not click Get Message unless the image is to be used for authent ...ty strings may be changed using security strings from SMS messages, mobile Phone Clients or using a TURing image. Do not click Request Image unless the TURi
    3 KB (393 words) - 12:52, 11 May 2017
  • ...One Time Code. The one time code can be sent by an SMS message or a mobile phone client. Do not click Get Message unless the image is to be used for authent ...ty strings may be changed using security strings from SMS messages, mobile Phone Clients or using a TURing image. Do not click Request Image unless the TURi
    3 KB (529 words) - 12:52, 11 May 2017
  • ...dows Mobile versions 6.x and earlier. For Windows Phone 7.x, see [[Windows Phone 7 How To Guide]]. ...op up from the Swivel server resets all the security strings on the mobile phone. You can use the device to get one-time codes for Swivel login and PIN chan
    8 KB (1,278 words) - 12:52, 11 May 2017
  • = The Swivel Windows Phone 8 2.0 App Overview = ...to download, configure and use this client. For other phones see [[Mobile Phone Client]] for earlier versions.
    10 KB (1,657 words) - 12:52, 11 May 2017
  • ...op up from the Swivel server resets all the security strings on the mobile phone. You can use the device to get one-time codes for Swivel login and PIN chan This application is for phones running Windows Phone 7.x only
    9 KB (1,383 words) - 12:52, 11 May 2017
  • <p>The Swivel virtual or hardware appliance must be reachable from the mobile phone to receive security codes</p> Swivel 3.8 and higher requires each mobile phone to be provisioned so it can be uniquely identified. Ensure that all Mobile
    13 KB (2,276 words) - 09:10, 19 May 2017
  • <p>The Swivel virtual or hardware appliance must be reachable from the mobile phone to receive security codes</p> Swivel 3.8 and higher requires each mobile phone to be provisioned so it can be uniquely identified. Ensure that all Mobile
    14 KB (2,480 words) - 15:05, 28 November 2017
  • ...imported from the repository. They are used to define email addresses and phone numbers for messaging, can be used to search in the user administration pag ...moving or adding country prefixes, additional notation etc. Therefore, the phone numbers need to be indicated.
    50 KB (8,368 words) - 08:13, 19 May 2017
  • <p>The Swivel virtual or hardware appliance must be reachable from the mobile phone to receive security codes</p> Swivel 3.8 and higher requires each mobile phone to be provisioned so it can be uniquely identified. Ensure that all Mobile
    13 KB (2,338 words) - 08:12, 19 May 2017
  • <p>The Swivel virtual or hardware appliance must be reachable from the mobile phone to receive security codes</p> Swivel 3.8 and higher requires each mobile phone to be provisioned so it can be uniquely identified. Ensure that all Mobile
    13 KB (2,159 words) - 08:11, 19 May 2017
  • ...hould be possible to authenticate by [[SMS]], hardware [[Token]], [[Mobile Phone Client]] and [[Taskbar How to Guide | Taskbar]] to verify that the RADIUS a
    5 KB (800 words) - 15:35, 25 October 2017
  • Swivel Mobile Phone Client Version v4 for One Touch Mobile client based solution. Mobile client users must install the Swivel Mobile Phone Client from the app store.
    2 KB (291 words) - 23:31, 2 January 2019
  • Swivel Mobile Phone Client Version v4 for One Touch Mobile client based solution. Mobile client users must install the Swivel Mobile Phone Client from the app store.
    4 KB (650 words) - 08:52, 28 September 2022
  • Swivel Mobile Phone Client Version v4 for One Touch Mobile client based solution. Push / OneTouch Mobile client users must install the Swivel Mobile Phone Client from the app store. You can see how that works on the following vide
    7 KB (1,023 words) - 16:32, 21 February 2019
  • ...e sent to the same destination as their security strings, usually a mobile phone number. This option allows the system administrator to ensure that provisi ;Support Email Address, Support Phone Number
    9 KB (1,479 words) - 08:58, 28 September 2022
  • <p>The Swivel virtual or hardware appliance must be reachable from the mobile phone to receive security codes</p> Swivel 3.8 and higher requires each mobile phone to be provisioned so it can be uniquely identified. Ensure that all Mobile
    13 KB (2,244 words) - 15:27, 18 May 2017
  • <p>The Swivel virtual or hardware appliance must be reachable from the mobile phone to receive security codes</p> Swivel 3.8 and higher requires each mobile phone to be provisioned so it can be uniquely identified. Ensure that all Mobile
    13 KB (2,343 words) - 15:26, 18 May 2017
  • *[[WP8V4.0|Windows Phone]]
    2 KB (334 words) - 17:21, 29 March 2019
  • | [[Swivel Core V4 Messaging Menu|Messaging]] || Mail and Mobile phone messaging configuration
    4 KB (563 words) - 09:43, 4 March 2020
  • ...rs sent from the Mobile app, to confirm that request is sent from the same phone as previous requests. ...ue OATH seed, allowing them to be used to perform OATH authentication. The phone then becomes a so-called "soft token".
    16 KB (2,548 words) - 08:34, 10 October 2022
  • * As message destinations - typically email addresses and phone numbers * '''Phone Number?''': if '''Yes''', then the attribute is subjected to certain modifi
    29 KB (4,787 words) - 13:22, 2 April 2024
  • ...both the OneTouch response and on the login form. (Just supported by Call Phone at the moment) ...needs to contain the session ID as the credential. (Just supported by Call Phone at
    19 KB (3,135 words) - 11:27, 3 February 2023
  • username,first-name,last-name,email,phone username,first-name,last-name,email,phone,group_1,group_2
    11 KB (1,785 words) - 09:54, 10 February 2022
  • == The Swivel Windows Phone 8 4.0 App Overview == Swivel Secure offers an updated Windows Phone 8 client for use with the Swivel platform. This article explains how to dow
    13 KB (2,338 words) - 14:59, 18 May 2017
  • == The Swivel Windows Phone 8 3.0 App Overview == Swivel Secure offers an updated Windows Phone 8 client for use with the Swivel platform. This article explains how to dow
    13 KB (2,198 words) - 15:00, 18 May 2017
  • ...user in a specified format (SMS text message, Turing TURing image, mobile phone client applicationapp, or email). <br> ...distributed through an SMS text message, email, TURuring image, or mobile phone client applicationapp. In this example, we will configure Swivel Sentry to
    10 KB (1,495 words) - 09:41, 18 May 2017
  • #REDIRECT [[Java Mobile Phone Client]]
    38 bytes (5 words) - 14:11, 18 May 2017
  • ...of the provisioning process, allowing authentications even when no mobile phone signal is present. * The Phone app to allow users to directly call their helpdesk from within the applicat
    1 KB (160 words) - 10:08, 31 May 2018
  • ...nd alter certain custom attributes for users - specifically Email address, Phone number, and given and family names. The application uses AdminRequest, so t
    7 KB (1,078 words) - 07:55, 25 June 2018
  • Swivel can provide Two Factor authentication with SMS, Token, and Mobile Phone Client and strong Single Channel Authentication with TURing or Pinpad, or i
    26 KB (3,903 words) - 10:48, 11 May 2020
  • <p>The Swivel virtual or hardware appliance must be reachable from the mobile phone to receive security codes</p> Swivel 4.05 and higher requires each mobile phone to be provisioned so it can be uniquely identified. Ensure that all Mobile
    13 KB (2,327 words) - 19:04, 21 November 2018
  • <p>The Swivel virtual or hardware appliance must be reachable from the mobile phone to receive security codes</p> Swivel 3.8 and higher requires each mobile phone to be provisioned so it can be uniquely identified. Ensure that all Mobile
    14 KB (2,316 words) - 19:46, 26 November 2018