Collect Charles Proxy logs to debug SSO issues in Creative Cloud mobile apps

Download and install the Charles Proxy. 

1. Connect your laptop to a wired network.
2. Open Sharing settings for the device.
3. Select Internet Sharing.

1. Find the network you are sharing.
2. Enter the password (if you set up authentication)
   1. On Android:
      
      1. Select the Advanced options check box.
         

b. For Proxy, select Manual.

c. For Proxy hostname, type in the ip address of your computer;

d. For Proxy port, enter 8888.

e. Click Save.

b. On iOS:

a. Go to Settings > Wi-Fi.

           b. Connect to your network.

c. After you are connected, click the connection.

d. Under HTTP Proxy, select Manual.

e. For Server, enter the IP address of your computer.

f. For Port, enter 8888.

1. Ensure that a Charles Proxy trusted certificate isn't already installed. If it is installed, and SSL Proxying is not working, remove the existing certificate. Then, perform the following steps.
2. On your computer, go to Help > SSL Proxying > Install Charles Root Certificate on a mobile device or remote browser.

3. In your device browser, open the link indicated in the dialog (chls.pro/ssl), and skip the proxy configuration.

4. Allow the certificate to download, and the install the certificate.

1. Open Charles Proxy, if it is not already open.
2. Open your mobile device's browser and navigate to a site.
3. Grant access when prompted that a device is trying to connect to your network.
4. You should now see your mobile device's traffic in your Charles Sequence log.

1. Open the app.
2. Go to the Sign In screen.
3. In Charles Proxy, identify the IMS host used by the application.

4. Go to Proxy > SSL Proxying Setting, and add the identified host (ims-na1.adobelogin.com) with port 443.

5. You should be able to see the unencrypted requests for the end point.

1. Go to Tools > Rewrite.
2. Perform the following configuration:

1. Open the mobile application.
2. Navigate to the Sign-in screen. Verify that you are prompted to sign in with your local IMS instance.