- *BASICS*
- The Knox Ecosystem
- White Paper
- Samsung Knox Portal
- Knox Cloud Services
- General Knox Support
- Knox Licenses
- *FOR IT ADMINS*
- Knox Admin Portal
- Knox Suite
- Knox Platform for Enterprise
- Introduction
- How-to videos
- Before you begin
- Get started with UEMs
- Introduction
- Blackberry UEM
- Citrix Endpoint Management
- FAMOC
- IBM MaaS360
- Microsoft Intune
- MobileIron Cloud
- MobileIron Core
- Samsung Knox Manage
- SOTI MobiControl
- VMware Workspace ONE UEM
- Knox Service Plugin
- Release notes
- Migrate to Android 11
- FAQs
- Troubleshoot
- KBAs
- Knox Mobile Enrollment
- Introduction
- How-to videos
- Get started
- Features
- Register resellers
- Add an admin
- Create profiles
- Google device owner support
- MDM compatibility matrices
- Device users
- Activity log
- Enroll and unenroll devices
- Configure devices
- Provide KME feedback
- Use the Knox Deployment App (KDA)
- Recover Google FRP locked devices using KME
- Role-based access control (RBAC)
- Release notes
- FAQs
- Troubleshoot
- KBAs
- On-Premise
- Knox Configure
- Mobile
- Wearables
- Shared Device
- KBAs
- Knox Capture
- Introduction
- How it works
- How-to videos
- IT admins: Get started
- Getting started with Knox Capture
- Step 1: Launch Knox Capture
- Step 2: Create a scanning profile
- Step 3: Select apps and activities
- Step 4: Configure the scanner
- Step 5: Set keystroke output rules
- Step 6: Test apps in your configuration
- Step 7: Share your configuration
- Step 8: Deploy Knox Capture in Managed mode
- End users: Get started
- Features
- Release notes
- FAQs
- Troubleshoot
- Knox Asset Intelligence
- Knox Manage
- Introduction
- How-to videos
- Get started
- Configure
- Licenses
- Organization
- Users
- Sync user information
- Groups
- Devices
- Content
- Applications
- Profile
- Knox E-FOTA
- Certificates
- Advanced settings
- Monitor
- Kiosk devices
- Remote Support
- Active Directory
- Microsoft Exchange
- Mobile Admin
- Appendix
- Release notes
- Features
- FAQs
- KBAs
- Knox E-FOTA
- Introduction
- How-to videos
- Get started
- Features
- EMM integration
- Appendix
- Release notes
- FAQs
- KBAs
- Troubleshoot
- Legacy Knox E-FOTA products
- Samsung Care+ for Business
- *FOR RESELLERS*
- Knox Deployment Program
- *FOR MANAGED SERVICE PROVIDERS*
- Knox MSP Program
Article ID: 115012110367 | Last Review: September 1, 2017 | Revision 1
[Environment]
Knox Workspace 2.0+
[Summary]
When I activate Common Criteria mode, I am unable to use Google Play.
[Cause]
Connection to Google Play is rejected because their servers do not meet CC mode requirements (MDFPP v2.0).
According to MDFPP v2.0 the TSF (TOE's security functions) verifies if the presented identifier matches the reference identifier according to RFC 6125.
The evaluator performs the following wildcard tests with each supported type of reference identifier:
As of now, Google's certificate do not satisfy the following tests.
According to MDFPP v2.0 the TSF (TOE's security functions) verifies if the presented identifier matches the reference identifier according to RFC 6125.
The evaluator performs the following wildcard tests with each supported type of reference identifier:
As of now, Google's certificate do not satisfy the following tests.
- The evaluator presents a server certificate containing a wildcard that is not in the left-most label of the presented identifier (e.g. foo.*.example.com) and verifies if the connection fails.
- The evaluator shall present a server certificate containing a wildcard in the left-most label (e.g. *.example.com). The evaluator configures the reference identifier with a single left-most label (e.g. foo.example.com) and verifies if the connection succeeds. The evaluator configures the reference identifier without a left-most label as in the certificate (e.g. example.com) and verifies if the connection fails. The evaluator configures the reference identifier with two left-most labels (e.g. bar.foo.example.come) and verifies if the connection fails.
[Resolution]
N/A
