Merge pull request NativeScript#1207 from NativeScript/etabakov/redes…

…ign-fixes fix: move sidekick images to sidekick folder
dankuck · Jun 21, 2018 · 64e33ba · 64e33ba
2 parents 57cfc51 + 9502e62
commit 64e33ba
Show file tree

Hide file tree

Showing 56 changed files with 44 additions and 44 deletions.
diff --git a/docs/sidekick/img/anchor.png b/docs/sidekick/img/anchor.png
diff --git a/docs/sidekick/img/api.png b/docs/sidekick/img/api.png
diff --git a/docs/sidekick/img/arrow.png b/docs/sidekick/img/arrow.png
diff --git a/docs/sidekick/img/close.png b/docs/sidekick/img/close.png
diff --git a/docs/sidekick/img/column.png b/docs/sidekick/img/column.png
diff --git a/docs/sidekick/img/enterprise-auth/AD-users.png b/docs/sidekick/img/enterprise-auth/AD-users.png
diff --git a/docs/sidekick/img/enterprise-auth/AzureAD.png b/docs/sidekick/img/enterprise-auth/AzureAD.png
diff --git a/docs/sidekick/img/enterprise-auth/app-auth-screen.png b/docs/sidekick/img/enterprise-auth/app-auth-screen.png
diff --git a/docs/sidekick/img/enterprise-auth/application-settings.png b/docs/sidekick/img/enterprise-auth/application-settings.png
diff --git a/docs/sidekick/img/enterprise-auth/applicationID.png b/docs/sidekick/img/enterprise-auth/applicationID.png
diff --git a/docs/sidekick/img/enterprise-auth/blue-bar.png b/docs/sidekick/img/enterprise-auth/blue-bar.png
diff --git a/docs/sidekick/img/enterprise-auth/client-secret.png b/docs/sidekick/img/enterprise-auth/client-secret.png
diff --git a/docs/sidekick/img/enterprise-auth/configure-single-sign-in.png b/docs/sidekick/img/enterprise-auth/configure-single-sign-in.png
diff --git a/docs/sidekick/img/enterprise-auth/create-application.png b/docs/sidekick/img/enterprise-auth/create-application.png
diff --git a/docs/sidekick/img/enterprise-auth/enable-access.png b/docs/sidekick/img/enterprise-auth/enable-access.png
diff --git a/docs/sidekick/img/enterprise-auth/endpoints1.png b/docs/sidekick/img/enterprise-auth/endpoints1.png
diff --git a/docs/sidekick/img/enterprise-auth/endpoints2.png b/docs/sidekick/img/enterprise-auth/endpoints2.png
diff --git a/docs/sidekick/img/enterprise-auth/enterprise-applications.png b/docs/sidekick/img/enterprise-auth/enterprise-applications.png
diff --git a/docs/sidekick/img/enterprise-auth/new-app-registration.png b/docs/sidekick/img/enterprise-auth/new-app-registration.png
diff --git a/docs/sidekick/img/enterprise-auth/non-gallery-app.png b/docs/sidekick/img/enterprise-auth/non-gallery-app.png
diff --git a/docs/sidekick/img/enterprise-auth/oauth-form-complete.png b/docs/sidekick/img/enterprise-auth/oauth-form-complete.png
diff --git a/docs/sidekick/img/enterprise-auth/oauth-form.png b/docs/sidekick/img/enterprise-auth/oauth-form.png
diff --git a/docs/sidekick/img/enterprise-auth/openid-form-complete.png b/docs/sidekick/img/enterprise-auth/openid-form-complete.png
diff --git a/docs/sidekick/img/enterprise-auth/openid-form.png b/docs/sidekick/img/enterprise-auth/openid-form.png
diff --git a/docs/sidekick/img/enterprise-auth/reply-urls.png b/docs/sidekick/img/enterprise-auth/reply-urls.png
diff --git a/docs/sidekick/img/enterprise-auth/required-permissions.png b/docs/sidekick/img/enterprise-auth/required-permissions.png
diff --git a/docs/sidekick/img/enterprise-auth/saml-based.png b/docs/sidekick/img/enterprise-auth/saml-based.png
diff --git a/docs/sidekick/img/enterprise-auth/saml-endpoints.png b/docs/sidekick/img/enterprise-auth/saml-endpoints.png
diff --git a/docs/sidekick/img/enterprise-auth/saml-form-complete.png b/docs/sidekick/img/enterprise-auth/saml-form-complete.png
diff --git a/docs/sidekick/img/enterprise-auth/saml-form.png b/docs/sidekick/img/enterprise-auth/saml-form.png
diff --git a/docs/sidekick/img/enterprise-auth/saml-settings-azure.png b/docs/sidekick/img/enterprise-auth/saml-settings-azure.png
diff --git a/docs/sidekick/img/enterprise-auth/selecting-authentication-service.png b/docs/sidekick/img/enterprise-auth/selecting-authentication-service.png
diff --git a/docs/sidekick/img/enterprise-auth/sidekick-templates.png b/docs/sidekick/img/enterprise-auth/sidekick-templates.png
diff --git a/docs/sidekick/img/enterprise-auth/signing-certificate.png b/docs/sidekick/img/enterprise-auth/signing-certificate.png
diff --git a/docs/sidekick/img/enterprise-auth/template-in-action.png b/docs/sidekick/img/enterprise-auth/template-in-action.png
diff --git a/docs/sidekick/img/enterprise-auth/tenant.png b/docs/sidekick/img/enterprise-auth/tenant.png
diff --git a/docs/sidekick/img/file.png b/docs/sidekick/img/file.png
diff --git a/docs/sidekick/img/getting-started.png b/docs/sidekick/img/getting-started.png
diff --git a/docs/sidekick/img/howdoi.png b/docs/sidekick/img/howdoi.png
diff --git a/docs/sidekick/img/icon-telerik-badge.png b/docs/sidekick/img/icon-telerik-badge.png
diff --git a/docs/sidekick/img/important.png b/docs/sidekick/img/important.png
diff --git a/docs/sidekick/img/logo.png b/docs/sidekick/img/logo.png
diff --git a/docs/sidekick/img/menu.png b/docs/sidekick/img/menu.png
diff --git a/docs/sidekick/img/nav-arrow.png b/docs/sidekick/img/nav-arrow.png
diff --git a/docs/sidekick/img/open.png b/docs/sidekick/img/open.png
diff --git a/docs/sidekick/img/search.png b/docs/sidekick/img/search.png
diff --git a/docs/sidekick/img/tap-logo.png b/docs/sidekick/img/tap-logo.png
diff --git a/docs/sidekick/img/troubleshooting/additional-components-required.png b/docs/sidekick/img/troubleshooting/additional-components-required.png
diff --git a/docs/sidekick/img/troubleshooting/certificatestoreutilities-stopped-working.png b/docs/sidekick/img/troubleshooting/certificatestoreutilities-stopped-working.png
diff --git a/docs/sidekick/img/troubleshooting/mark-key-as-exportable.png b/docs/sidekick/img/troubleshooting/mark-key-as-exportable.png
diff --git a/docs/sidekick/img/tutorials.png b/docs/sidekick/img/tutorials.png
diff --git a/docs/sidekick/troubleshooting/frequently-asked-questions.md b/docs/sidekick/troubleshooting/frequently-asked-questions.md
@@ -12,7 +12,7 @@ slug: frequently-asked-questions
 
 After updating the {{ site.ns-sk }} client, you might see the following error message on launch:
 
-![](/images/troubleshooting/additional-components-required.png)
+![](../img/troubleshooting/additional-components-required.png)
 
 To resolve this issue, you need to update the {{ site.ns-cli }} to the required (in most cases, the latest available) version. To do this, you should open a command prompt (on Windows) or a terminal (on macOS and Linux) and run the following command:
 
@@ -24,10 +24,10 @@ After the installation process is complete, you will no longer see the error men
 
 On a Windows machine, when you build in the cloud for iOS or Android with a certificate stored in the Windows Certificate Manager, you might encounter the following error:
 
-![](/images/troubleshooting/certificatestoreutilities-stopped-working.png)
+![](../img/troubleshooting/certificatestoreutilities-stopped-working.png)
 
 This issue will occur when the selected certificate is not a valid iOS or Android certificate or when you have not enabled the "Mark this key as exportable..." option when importing the certificate to the Windows Certificate Manager. To resolve the latter, you need to enable the option when importing the certificate as shown in the image below:
 
-![](/images/troubleshooting/mark-key-as-exportable.png)
+![](../img/troubleshooting/mark-key-as-exportable.png)
 
 Marking the key as exportable will resolve the error, as long as the provided certificate is a valid iOS or Android one.
diff --git a/docs/sidekick/user-guide/enterprise-auth/intro.md b/docs/sidekick/user-guide/enterprise-auth/intro.md
@@ -24,19 +24,19 @@ Let’s look at how it works.
 
 As a first step, [create a new app]({% slug create-app-from-template %}) using the Enterprise Auth template.
 
-![](/images/enterprise-auth/sidekick-templates.png)
+![](../../img/enterprise-auth/sidekick-templates.png)
 
 Give your app a name, and click **Create**. Sidekick will take a minute to scaffold your app. When it finishes, click the **Configure** button in the blue bar to start setting up the connection to your enterprise auth provider.
 
-![](/images/enterprise-auth/blue-bar.png)
+![](../../img/enterprise-auth/blue-bar.png)
 
 <h2 id="step-2">Step 2. Select a protocol</h2>
 
 > **WARNING**: Completing this authentication setup can be hard, as the information you need to obtain varies depending on your auth provider. Therefore, you might need to work with your IT admins to help get the information that you need to make the connection, especially if you're not familiar with the infrastructure behind your auth setup.
 
 On the Enterprise Auth screen the first thing you’ll see is a collection of radio buttons, asking you to choose between **SAML-Redirect**, **OpenID Connect**, and **OAuth 2**.
 
-![](/images/enterprise-auth/selecting-authentication-service.png)
+![](../../img/enterprise-auth/selecting-authentication-service.png)
 
 Knowing which service you need means knowing a little bit about your enterprise authentication provider. Some providers only support one of the above protocols, while others allow you to choose between the protocol you prefer.
 
@@ -58,11 +58,11 @@ After you’ve completed the authentication setup, your last step is to run your
 
 After Sidekick deploys your new app to your device(s) you should see an app that looks like this.
 
-![](/images/enterprise-auth/template-in-action.png)
+![](../../img/enterprise-auth/template-in-action.png)
 
 When you tap the **Log in** button, if all went well, you should be prompted to authenticate with your enterprise authentication provider. In the case of our Microsoft Azure-based example, the app prompts the user to authenticate with their Microsoft account.
 
-![](/images/enterprise-auth/app-auth-screen.png)
+![](../../img/enterprise-auth/app-auth-screen.png)
 
 > **NOTE**: Configuring enterprise authentication providers is very tricky. If you’re not seeing your auth screen as expected, or if you hit problems at any time throughout the process, feel free to [reach out on the NativeScript community forum](https://discourse.nativescript.org/c/Sidekick).
 

diff --git a/docs/sidekick/user-guide/enterprise-auth/oauth2.md b/docs/sidekick/user-guide/enterprise-auth/oauth2.md
@@ -14,7 +14,7 @@ NativeScript Sidekick gives you the ability to connect to enterprise authenticat
 
 The first thing you need to do to configure an OAuth 2 connection is to visit the **Enterprise Auth** screen and select the **OAuth 2** radio button. You should see a form that looks like this.
 
-![](/images/enterprise-auth/oauth-form.png)
+![](../../img/enterprise-auth/oauth-form.png)
 
 Let’s start by looking at the fields you need to provide to connect to your enterprise authentication provider. Then, as an example, we'll explore how we'd complete the form for a project using Azure Active Directory.
 
@@ -86,39 +86,39 @@ The following steps will walk you through creating a new Azure Active Directory
 
 1. From within the [Azure portal](https://portal.azure.com), click on Azure Active Directory or click on **+New** and search for Azure Active Directory.
 
-	![Azure AD](/images/enterprise-auth/AzureAD.png)
+	![Azure AD](../../img/enterprise-auth/AzureAD.png)
 
 2. Choose the **App Registrations** option and **New Application Registration**.
 
-	![App registrations](/images/enterprise-auth/new-app-registration.png)
+	![App registrations](../../img/enterprise-auth/new-app-registration.png)
 
 3. Enter a name for the application (this can be any name you prefer), choose **Web app / API** and, for the Sign-on URL, enter `https://auth.kinvey.com`.
 
-	![new app registration](/images/enterprise-auth/create-application.png)
+	![new app registration](../../img/enterprise-auth/create-application.png)
 
 4. Once it is created, choose **Reply URLs**.
 
-	![application settings](/images/enterprise-auth/application-settings.png)
+	![application settings](../../img/enterprise-auth/application-settings.png)
 
 5. Enter `https://auth.kinvey.com/oauth2/redirect` (see the [Kinvey docs](https://devcenter.kinvey.com/html5/guides/mobile-identity-connect#ConfiguringyourOAuth2IdentityProvidertoacceptKinveyRequests) for additional details)
 
-	![Reply URLs](/images/enterprise-auth/reply-urls.png)
+	![Reply URLs](../../img/enterprise-auth/reply-urls.png)
 
 6. Back in the application settings, choose **Required Permissions** and then **Windows Azure Active Directory**.
 
-	![required permissions](/images/enterprise-auth/required-permissions.png)
+	![required permissions](../../img/enterprise-auth/required-permissions.png)
 
 7. Enable the following:
 
 	* Access the directory as the signed-in user
 	* Read all users' basic profiles
 	* Sign in and read user profile
 
-	![enable access](/images/enterprise-auth/enable-access.png)
+	![enable access](../../img/enterprise-auth/enable-access.png)
 
 8. Back in the application settings again, choose **Keys** and create a new option under **Passwords**. Set the description (this can be any text you prefer) and expiration (for example, "never"). Click **Save**. Be sure to copy the key's value before leaving.
 
-	![client secret](/images/enterprise-auth/client-secret.png)
+	![client secret](../../img/enterprise-auth/client-secret.png)
 
 In order to test the log in process, Azure Active Directory will need a user. To assing a user to this enterprise application, click on "Assign a user for testing" in the quick start or "Users and groups" in the enterprise application sub-navigation. For testing purposes, you could add yourself.
 
@@ -129,15 +129,15 @@ Now that our Azure Active Directory is set up, let's look at the values within A
 * **Name**: Any name you choose.
 * **Provider URI** and **Grant Endpoint**: To get these values from within Azure, go to Azure Active Directory, choose **App registrations** and then **Endpoints**.
 
-  ![Choosing the endpoints](/images/enterprise-auth/endpoints1.png)
+  ![Choosing the endpoints](../../img/enterprise-auth/endpoints1.png)
 
   On the subsequent page, the Provider URI is the OAuth 2.0 Token Endpoint value and the Grant Endpoint is the OAuth 2.0 Authorization Endpoint value.
 
-  ![Endpoints list](/images/enterprise-auth/endpoints2.png)
+  ![Endpoints list](../../img/enterprise-auth/endpoints2.png)
 
 * **Client ID** is the application ID found by going to Azure Active Directory and then choosing **App registrations**.
 
-  ![Application ID](/images/enterprise-auth/applicationID.png)
+  ![Application ID](../../img/enterprise-auth/applicationID.png)
 
 * **Client Secret** is the value of the key created in step 8 above. If you did not copy the key during that step, it is hidden and you'll simply need to create a new key.
 * **User ID Attribute** and **User ID Endpoint** can both be blank.
@@ -146,7 +146,7 @@ Now that our Azure Active Directory is set up, let's look at the values within A
 
 When you’re done, your form should look something like this in Sidekick.
 
-![](/images/enterprise-auth/oauth-form-complete.png)
+![](../../img/enterprise-auth/oauth-form-complete.png)
 
 Click the **Save Service** button and you are ready to move on to building and testing your NativeScript mobile app.
 

diff --git a/docs/sidekick/user-guide/enterprise-auth/openid.md b/docs/sidekick/user-guide/enterprise-auth/openid.md
@@ -14,7 +14,7 @@ NativeScript Sidekick gives you the ability to connect to enterprise authenticat
 
 The first thing you need to do to configure an OpenID connection is to visit the **Enterprise Auth** screen and select the **OpenID Connect** radio button. You should see a form that looks like this.
 
-![](/images/enterprise-auth/openid-form.png)
+![](../../img/enterprise-auth/openid-form.png)
 
 Let’s start by looking at the fields you need to provide to connect to your enterprise authentication provider. Then, as an example, we'll explore how we'd complete the form for a project using Azure Active Directory.
 
@@ -74,39 +74,39 @@ The following steps will walk you through creating a new Azure Active Directory
 
 1. From within the [Azure portal](https://portal.azure.com), click on Azure Active Directory or click on **+New** and search for Azure Active Directory.
 
-	![Azure AD](/images/enterprise-auth/AzureAD.png)
+	![Azure AD](../../img/enterprise-auth/AzureAD.png)
 
 2. Choose the **App Registrations** option and **New Application Registration**.
 
-	![App registrations](/images/enterprise-auth/new-app-registration.png)
+	![App registrations](../../img/enterprise-auth/new-app-registration.png)
 
 3. Enter a name for the application (this can be any name you prefer), choose **Web app / API** and, for the Sign-on URL, enter `https://auth.kinvey.com`.
 
-	![new app registration](/images/enterprise-auth/create-application.png)
+	![new app registration](../../img/enterprise-auth/create-application.png)
 
 4. Once it is created, choose **Reply URLs**.
 
-	![application settings](/images/enterprise-auth/application-settings.png)
+	![application settings](../../img/enterprise-auth/application-settings.png)
 
 5. Enter `https://auth.kinvey.com/oidc/redirect` (see the [Kinvey docs](https://devcenter.kinvey.com/html5/guides/mobile-identity-connect#ConfiguringyourOpenIDConnectIdentityProvidertoacceptKinveyRequests) for additional details).
 
-	![Reply URLs](/images/enterprise-auth/reply-urls.png)
+	![Reply URLs](../../img/enterprise-auth/reply-urls.png)
 
 6. Back in the application settings, choose **Required Permissions** and then **Windows Azure Active Directory**.
 
-	![required permissions](/images/enterprise-auth/required-permissions.png)
+	![required permissions](../../img/enterprise-auth/required-permissions.png)
 
 7. Enable the following:
 
 	* Access the directory as the signed-in user
 	* Read all users' basic profiles
 	* Sign in and read user profile
 
-	![enable access](/images/enterprise-auth/enable-access.png)
+	![enable access](../../img/enterprise-auth/enable-access.png)
 
 8. Back in the application settings again, choose **Keys** and create a new option under **Passwords**. Set the description (this can be any text you prefer) and expiration (for example, "never"). Click **Save**. Be sure to copy the key's value before leaving.
 
-	![client secret](/images/enterprise-auth/client-secret.png)
+	![client secret](../../img/enterprise-auth/client-secret.png)
 
 In order to test the log in process, Azure Active Directory will need a user. To add a user, go to Active Directory, click **Users and Groups**, then **All Users**, and finally **New User**. For testing purposes, you could add yourself.
 
@@ -123,20 +123,20 @@ Now that our Azure Active Directory is set up, let's look at the values within A
 
   The value of `{tenant}` is an identifier with Azure for your account. This information can be found by clicking on Azure Active Directory and choosing **Properties**. The value of `{tenant}` is the value listed for **Directory ID**.
 
-  ![Finding your tenant](/images/enterprise-auth/tenant.png)
+  ![Finding your tenant](../../img/enterprise-auth/tenant.png)
 
   Replace the value of `{tenant}` in the URL and navigate to it. This page will contain some JSON formatted values. The value for Provider URI is listed as `token_endpoint`. The value for Grant Endpoint is listed as `authorization_endpoint`. Finally, the value for Issuer Identifier is listed as `issuer`
 
 * **Client ID** is the application ID found by going to Azure Active Directory and then choosing **App registrations**.
 
-  ![Application ID](/images/enterprise-auth/applicationID.png)
+  ![Application ID](../../img/enterprise-auth/applicationID.png)
 
 * **Client Secret** is the value of the key created in step 8 above. If you did not copy the key during that step, it is hidden and you'll simply need to create a new key.
 * **Scope** should be set to `email` to give your app access to the user's email address.
 
 When you’re done, your form should look something like this in Sidekick.
 
-![](/images/enterprise-auth/openid-form-complete.png)
+![](../../img/enterprise-auth/openid-form-complete.png)
 
 Click the **Save Service** button and you are ready to move on to building and testing your NativeScript mobile app.
 

diff --git a/docs/sidekick/user-guide/enterprise-auth/saml.md b/docs/sidekick/user-guide/enterprise-auth/saml.md
@@ -16,7 +16,7 @@ NativeScript Sidekick gives you the ability to connect to enterprise authenticat
 
 The first thing you need to do to configure a SAML-Redirect connection is to visit the **Enterprise Auth** screen and select the **SAML-Redirect** radio button. You should see a form that looks like this.
 
-![](/images/enterprise-auth/saml-form.png)
+![](../../img/enterprise-auth/saml-form.png)
 
 Let’s start by looking at the fields you need to provide to connect to your enterprise authentication provider. Then, as an example, we'll explore how we'd complete the form for a project using Azure Active Directory.
 
@@ -64,23 +64,23 @@ The following steps will walk you through creating a new Azure Active Directory
 
 1. From within the [Azure portal](https://portal.azure.com), click on Azure Active Directory or click on +New and search for Azure Active Directory.
 
-	![Azure AD](/images/enterprise-auth/AzureAD.png)
+	![Azure AD](../../img/enterprise-auth/AzureAD.png)
 
 2. Choose the **App Registrations** option and **Enterprise applications**.
 
-	![Enterprise applications](/images/enterprise-auth/enterprise-applications.png)
+	![Enterprise applications](../../img/enterprise-auth/enterprise-applications.png)
 
 3. Click **+ New application** and then choose **Non-gallery application**. Give your application a name (this can be whatever you like) and click **Add**.
 
-  ![Non-gallery application](/images/enterprise-auth/non-gallery-app.png)
+  ![Non-gallery application](../../img/enterprise-auth/non-gallery-app.png)
 
 4. Click on **Configure single sign-on**.
 
-![Configure single sign-on](/images/enterprise-auth/configure-single-sign-in.png)
+![Configure single sign-on](../../img/enterprise-auth/configure-single-sign-in.png)
 
 5. Choose **SAML-based Sign-on** from the drop down.
 
-  ![SAML-based sign-on](/images/enterprise-auth/saml-based.png)
+  ![SAML-based sign-on](../../img/enterprise-auth/saml-based.png)
 
 6. Fill in the following values:
 
@@ -89,11 +89,11 @@ The following steps will walk you through creating a new Azure Active Directory
   * Click on **Show sdvanced URL settings**.
   * For **Sign on URL** enter `https://auth.kinvey.com/`.
 
-  ![Azure SAML settings](/images/enterprise-auth/saml-settings-azure.png)
+  ![Azure SAML settings](../../img/enterprise-auth/saml-settings-azure.png)
 
 7. Scroll down to the SAML Signing Certificate. If it is not active yet, enable it and then download the Base64 version. (More details about managing signing certificates within Azure can be found in their [documentation](https://docs.microsoft.com/en-us/azure/active-directory/active-directory-sso-certs).)
 
-  ![Base64 signing certificate](/images/enterprise-auth/signing-certificate.png)
+  ![Base64 signing certificate](../../img/enterprise-auth/signing-certificate.png)
 
 8. Click the **Save** button to save your settings.
 
@@ -106,18 +106,18 @@ Now that our Azure Active Directory is set up, let's look at the values within A
 * **Name**: Any name you choose.
 * **Provider URI**: To get this value from within Azure, go to Azure Active Directory, choose **App registrations** and then **Endpoints**.
 
-  ![Choosing the endpoints](/images/enterprise-auth/endpoints1.png)
+  ![Choosing the endpoints](../../img/enterprise-auth/endpoints1.png)
 
   On the subsequent page, the Provider URI is the SAML-P Sign-on Endpoint value value.
 
-  ![Endpoints list](/images/enterprise-auth/saml-endpoints.png)
+  ![Endpoints list](../../img/enterprise-auth/saml-endpoints.png)
 
 * **Certificate text** is the contents of the Base64 signing certificate you downloaded. Open the file using a text editor and copy the contents between the `-----BEGIN CERTIFICATE-----` and `-----END CERTIFICATE-----` lines into the form field.
 * **Name ID Format URI** for Azure Active Directory should be `urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress`. (You can find more information about the various values Azure accepts here and what they mean in their [documentation](https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-single-sign-on-protocol-reference#nameidpolicy).)
 
 When you’re done, your form should look something like this in Sidekick.
 
-![](/images/enterprise-auth/saml-form-complete.png)
+![](../../img/enterprise-auth/saml-form-complete.png)
 
 Click the **Save Service** button and you are ready to move on to building and testing your NativeScript mobile app.