In F5 Access 2.1.1, the session variable _fingerprint was not populated when an on-demand connection was completed. Refer to Client SSL Profile configuration for details. In order to leverage the ATS-enabled F5 Access for iOS the BIG-IP should be configured to use secure protocols and encryption algorithms that satisfy ATS requirements. TLS connections require compliance with best practices: TLSv1.2 with forward secrecy, no known-insecure cryptographic primitives (RC4 encryption, SHA-1 certificate signatures), and key size requirements (2048 bits for RSA, 256 bits for EC).The app will not be allowed to initiate plaintext HTTP connections, and will be required to use HTTPS with the strongest TLS configuration (TLS 1.2 and PFS cipher suites).App Transport Security (ATS) requires that beginning with iOS 9 apps no longer be allowed to initiate insecure plain text HTTP connections, or TLS connections that don't comply with stricter requirements. Starting with F5 Access version 3.0, the client is distributed with App Transport Security enabled.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |