DOCSLIB.ORG

RSA Adaptive Authentication (Hosted) 11 Programmer's Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
RSA Adaptive Authentication (Hosted) 11 Programmer's Guide RSA Adaptive Authentication (Hosted) Programmer's Guide Contact Information Go to the RSA corporate web site for regional Customer Support telephone and fax numbers: www.rsa.com Trademarks RSA, the RSA Logo and EMC are either registered trademarks or trademarks of EMC Corporation in the United States and/or other countries. All other trademarks used herein are the property of their respective owners. For a list of RSA trademarks, go to www.rsa.com/legal/trademarks_list.pdf. License agreement This software and the associated documentation are proprietary and confidential to EMC, are furnished under license, and may be used and copied only in accordance with the terms of such license and with the inclusion of the copyright notice below. This software and the documentation, and any copies thereof, may not be provided or otherwise made available to any other person. No title to or ownership of the software or documentation or any intellectual property rights thereto is hereby transferred. Any unauthorized use or reproduction of this software and the documentation may be subject to civil and/or criminal liability. This software is subject to change without notice and should not be construed as a commitment by EMC. Note on encryption technologies This product may contain encryption technology. Many countries prohibit or restrict the use, import, or export of encryption technologies, and current use, import, and export regulations should be followed when using, importing or exporting this product. Distribution Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Copyright © 2012-2014 EMC Corporation. All Rights Reserved. October 2012 Revised: July 2014 RSA Adaptive Authentication (Hosted) Programmer’s Guide Contents Preface................................................................................................................................... 7 About This Guide................................................................................................................ 7 RSA Adaptive Authentication (Hosted) Documentation.................................................... 7 Support and Service ............................................................................................................ 8 Before You Call Customer Support............................................................................. 9 Chapter 1: Overview of RSA Adaptive Authentication...........................11 Risk Models ...................................................................................................................... 12 Anti-Fraud Model ...................................................................................................... 12 Anti-Intrusion Model ................................................................................................. 13 General Workflow............................................................................................................. 13 RSA Adaptive Authentication Decision Flow and Module Relationship ................. 14 SOAP Messages......................................................................................................... 15 Integration Points .............................................................................................................. 16 Protocols and Message Formats........................................................................................ 17 SOAP API.................................................................................................................. 17 Message Structure and Format .................................................................................. 17 Transport Protocols.................................................................................................... 19 Web Services URLs and Multiple Version Support ......................................................... 20 Security ............................................................................................................................. 21 Transport Security...................................................................................................... 21 Application Security .................................................................................................. 21 Data Integrity ............................................................................................................. 22 Integration Options ........................................................................................................... 22 SOAP API.................................................................................................................. 22 SOAP API with Authentication Data Stored at Organization’s Site ......................... 22 SOAP API and HTML Redirection........................................................................... 23 FI-Defined Authentication Method ........................................................................... 23 Chapter 2: Initial Data Collection........................................................................ 25 Collection for Challenge Questions Authentication ......................................................... 25 Stage I - Analyze Message......................................................................................... 27 Stage II - Query.......................................................................................................... 27 Stage III - Authentication Data Collection ................................................................ 28 Collection for Out-of-band Phone and Out-of-band SMS Authentication ....................... 30 Stage I - Analyze Message......................................................................................... 31 Stage II - Collection................................................................................................... 31 Stage III - Authentication Data Collection ................................................................ 32 Chapter 3: SOAP API Use Cases ........................................................................ 33 RSA Adaptive Authentication API Message Flow........................................................... 33 Contents 3 RSA Adaptive Authentication (Hosted) Programmer’s Guide Challenge Questions Authentication Use Case................................................................. 36 Stage I - Logon Process ............................................................................................. 37 Stage II - Analyze Message ....................................................................................... 37 Stage III - Challenge .................................................................................................. 38 Stage IV - Authenticate.............................................................................................. 38 Out-of-Band Phone Authentication Use Case .................................................................. 39 Stage I - Logon Process ............................................................................................. 40 Stage II - Analyze Message ....................................................................................... 40 Stage III - Query ........................................................................................................ 41 Stage IV - Challenge.................................................................................................. 41 Stage V - QueryAuthStatus........................................................................................ 42 Out-of-Band SMS Authentication Use Case .................................................................... 43 Stage I - Logon Process ............................................................................................. 44 Stage II - Analyze Message ....................................................................................... 44 Stage III - Query ........................................................................................................ 45 Stage IV - Challenge.................................................................................................. 45 Stage V - Authenticate............................................................................................... 46 Knowledge-Based Authentication Use Case .................................................................... 47 Stage I - Logon Process ............................................................................................. 49 Stage II - Analyze Message ....................................................................................... 49 Stage III - Challenge .................................................................................................. 49 Stage IV - Authenticate.............................................................................................. 50 One-Time Password Authentication Use Case ................................................................. 51 Stage I - Logon Process ............................................................................................
Load more

Recommended publications
  • 2015 Global Payments Guide
    TREASURY SERVICES 2015 Global Payments Guide Your Guide To Making Cross-Currency Payments in over 150 Countries with Ease. 2015 Global Payments Guide Last Updated: July 29, 2015 For the most up-to-date version, please visit jpmorgan.com/visit/guide | 2 The J.P. Morgan Global Payments Guide is your desktop resource to help you make timely and accurate payments to beneficiaries around the world. Work with J.P. Morgan to get the global payment support that Setting up your payment SWIFT BIC your business demands When setting up a payment, basic identifying information is SWIFT BIC, BIC, SWIFT ID or SWIFT refers to the ISO 9362 With employees, suppliers and operations located around the required. Additional information may be required by countries with restricted currencies. unique bank identifier code of a particular bank. They are globe, ensuring prompt payments in multiple currencies is a used to ensure automated and accurate identification of challenge. Your business requires a partner who takes the J.P. Morgan may use third party vendors for processing financial institutions within payment systems when messages time to understand your needs and helps ensure your payments in certain exotic currencies. These third party or money is transferred. payments are processed smoothly. vendors may require beneficiaries to provide supporting The BIC format contains a minimum of 8 and a maximum of As one of the top-ranked cash management and payments documents for regulatory purposes in some countries. 11 alphanumeric characters. processors in the world, J.P. Morgan is able to offer the tools Basic Information that help you manage your day-to-day global operations, Example: CHASUS33XXX o Full beneficiary name along with your more sophisticated foreign exchange needs.
    [Show full text]
  • Documento Ayuda
    TRANSFERENCIAS AL EXTERIOR Beneficios Realiza transferencias al exterior desde nuestras más de 450 Agencias BCP a nivel nacional o desde la comodidad de tu casa a través de nuestra Banca por Internet. @ Recibe la confirmación de tus transferencias y el SWIFT automáticamente vía correo electrónico. Para ello deberás indicar tu correo electrónico en la solicitud. Seguridad: Las transferencias se trasmiten con claves encriptadas (vía sistema SWIFT). Características El importe mínimo a transferir es de USD 100.00 o su equivalente en otras monedas. Las transferencias al exterior están afectas al cobro del ITF. Tiempo de llegada de una transferencia al banco corresponsal de destino según horario de recepción de solicitud: TIEMPO DE LLEGADA AL BANCO CORRESPONSAL DE DESTINO PARA TRANSFERENCIAS AL EXTERIOR EN DÓLARES AMERICANOS MISMO DÍA SIGUIENTE DÍA ÚTIL (T+1) DOS DÍAS ÚTILES (T+2) RECIBIDA HASTA LAS RECIBIDA ENTRE LAS U.S.A. Y AMÉRICA LATINA 12:00 PM (MEDIO DÍA) 12:01 PM Y 04:00 PM RECIBIDA HASTA LAS RECIBIDA ENTRE LAS EUROPA 12:00 PM (MEDIO DÍA) 12:00 PM Y 04:00 PM RECIBIDA ENTRE LAS ASIA 8:00 AM Y 04:00 PM TIEMPO DE LLEGADA AL BANCO CORRESPONSAL DE DESTINO PARA TRANSFERENCIAS AL EXTERIOR EN OTRAS MONEDAS DISTINTAS AL DÓLAR MISMO DÍA SIGUIENTE DÍA ÚTIL (T+1) DOS DÍAS ÚTILES (T+2) RECIBIDA HASTA LAS U.S.A. Y AMÉRICA LATINA 12:00 PM (MEDIO DÍA) RECIBIDA HASTA LAS EUROPA 12:00 PM (MEDIO DÍA) RECIBIDA HASTA LAS ASIA 12:00 PM (MEDIO DÍA) 1 ANEXO 1: ¿CÓMO IDENTIFICAR LA CUENTA DE ABONO DEL BENEFICIARIO EN UNA TRANSFERENCIA AL EXTERIOR? Las cuentas de abono de los beneficiarios dentro de otros bancos en el exterior se identifican según tipos de códigos y dependiendo de la región donde se ubiquen pueden ser: 1.
    [Show full text]
  • Payment Formatting Guidelines
    PAYMENT FORMATTING GUIDELINES 10.2018 Version 6.2 kpcu.com PAYMENT FORMATTING GUIDELINES Welcome to the October 2018 edition of the Payment Formatting Guidelines (PFG). In response to newly implemented payment requirements, we will be updating the following: • AUD (Australian Dollar), Beneficiary Account requirements • ARS (Argentine Peso), full beneficiary address required • ILS (Israeli Shekel), payments to Palestine require a 29 character IBAN • INR (Indian Rupee), P1401 POP code added back to list • MXN (Mexican Peso), beneficiary tax ID required: - Tax ID character length for INDIVIDUAL = 13 or 18 alphanumeric digits - Tax ID character length for BUSINESS = 12 alphanumeric digits • MXN (Mexican Peso), Recommendation: Beneficiary name should not include initials. Beneficiary names must consist of 3 or more letters. • NAD (Namibian Dollar), beneficiary bank branch address requirement removed • PHP (Philippines Peso), beneficiary bank branch address requirement removed • TWD (New Taiwan Dollar), Chunghwa Post Co., Ltd. will not accept TWD payments • SGD (Singapore Dollars), beneficiary bank account requirements amended to 5-14 digits, branch code required for payments to HSBC, OCBS or SBI. • NPR (Nepalese Rupee), (Removed) ADDITIONAL CONSIDERATIONS: Payments to Nepalese Nationals in Nepal can be done in NPR only. We are also happy to include requirements for the following new currencies: AWG (Arubian Florin); CDF (Congolese Franc); MDL (Maldavian Lieu); MNT (Mongolian Tugrik); MRU (Mauritanian Olguiya); STN (Dobra); and IQD (Iraqi Dinar). TABLE OF CONTENTS CURRENCY GUIDELINES �����������������������������������������������������������������������������������������������������������������������������������������������������3 MAXIMIZING THE USE OF THIS DOCUMENT . .3 BBAN/BASIC BANK ACCOUNT NUMBER . .3 IBAN/INTERNATIONAL BANK ACCOUNT NUMBER . .3 SWIFT/BIC CODE . .4 BANK CODE . .4 NON-SWIFT BIC . .5 BENEFICIARY ADDRESS .
    [Show full text]
  • Payment Formatting Guidelines
    PAYMENT FORMATTING GUIDELINES 03.2014 Version 2.7 business.westernunion.com Page 1 of 77 business.westernunion.com TABLE OF CONTENTS CURRENCY GUIDELINES ................................................................................. 3 MAXIMIZING THE USE OF THE GUIDELINES .................................................. 3 BBAN / BASIC ACCOUNT NUMBER .................................................................. 3 IBAN / ACCOUNT NUMBER ............................................................................... 3 SWIFT / BIC CODE ............................................................................................. 4 BANK CODE ....................................................................................................... 4 NON-SWIFT BIC ................................................................................................. 5 ADDITIONAL REQUIREMENTS ........................................................................ 5 IBAN & SWIFT CODE COUNTRIES ................................................................... 6 COUNTRY CURRENCIES (BY CURRENCY CODE) CURRENCIES A - E ............................................................................................ 7 EURO IBAN REQUIREMENTS ......................................................................... 21 CURRENCIES F - J .......................................................................................... 29 CURRENCIES K - O ......................................................................................... 35 CURRENCIES P - T .........................................................................................
    [Show full text]
  • PAYMENT GUIDELINES Frequently Asked Questions & Definitions
    ROTARY INTERNATIONAL PAYMENT GUIDELINES Frequently Asked Questions & Definitions Where can I find the banking information requested on the payee form/What information is required to make an electronic transfer into my account? There are different requirements in different countries depending on your country’s banking regulations (see the Payment Guidelines for Rotarians: http://www.rotary.org/RIdocuments/en_pdf/rits_payment_guidelines_en.pdf ). It is helpful to visit your bank and ask them to help provide you with the appropriate information listed on the payee form as they may be more familiar with the type of information required. General requirements for electronic funds transfers are listed below. Please also see the definitions below for an explanation of the various bank codes required to make payments. Why does Rotary need my bank information to make a payment? As banking becomes more and more electronic worldwide, checks and paper-based payment methods are becoming less common because they are considerably less efficient, less secure and much more costly to process. Already, virtually all of Rotary’s cross border banking transactions are being made via electronic transfers and a significant number of domestic payments are made electronically as well. While all bank transfers can be subject to fees, most recipients of domestic transfers pay minimal to no fees. The best way for Rotary to keep these fees minimal, from the perspective of both the recipient of funds and the sender, is to provide complete and correct account information to the bank through which the funds are being sent, including all required bank codes. By providing complete and correct account information initially, including instructions to make payments via the preferred payment method, Rotarians help us to keep payment processing costs low and to send funds more quickly and efficiently.
    [Show full text]
  • Consumer International Wire Transfers One of the Fastest Ways to Move Money Around the World
    2020 Consumer international wire transfers One of the fastest ways to move money around the world Important information about your request To ensure timely delivery to the recipient, please provide complete information. Obtain complete wiring instructions, including account and routing information from the beneficiary. If you are unsure of the Beneficiary information and bank routing instructions, always contact the recipient who should confirm the information with their bank. Sending international wires without the required information can cause the wire to be delayed, or returned. To help prevent fraudulent wire transfers, please discuss the purpose of your wire transfer with a banker. Be cautious before sending money to someone you don’t know or met through social media. Common scams include requests to pay IRS taxes, emergency needs by family members, telemarketing sales calls, Internet purchases, etc. Required information for sending a international wire transfer STEP1 Please note, wire transfers must be conducted in person at a U.S. Bank branch Monday – Friday prior to 3 p.m. Central time (excludes U.S. Bank holidays). Originator Purpose of the wire transfer __________________________________________________ (sender) ___________________________________________________________________________ o Name ___________________________________________________________________ o Address ________________________________________________________________ o Telephone number _______________________________________________________ o Originator’s relationship
    [Show full text]
  • Payment Formatting Guidelines August 2021 Version 2021.2 Payment Formatting Guidelines
    Payment formatting guidelines August 2021 Version 2021.2 Payment Formatting Guidelines Table of contents Currency guidelines ���������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������4 Maximizing the use of this document . .4 BBAN/Basic Bank Account Number �����������������������������������������������������������������������������������������������������������������������������������������������������������4 IBAN/International Bank Account Number �����������������������������������������������������������������������������������������������������������������������������������������������4 SWIFT/BIC code �����������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������5 Bank code �������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������5 Non-SWIFT BIC . .6 Beneficiary Address ���������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������6 Additional requirements �������������������������������������������������������������������������������������������������������������������������������������������������������������������������������6
    [Show full text]