Creating Backend Settings with API Configuration

A Backend configuration is needed to preview and publish an application developed in Kuika. To configure the backend of the application you have developed, you must make the necessary adjustments to the API through Kuika Configuration Manager.

This training content consists of the following topics. For API Configuration;
1.Creating a new Configuration in Kuika
2.Adding Application Configuration information
3.Adding the Authentication Provider
4.Adding the Password Policy
5.Adding Email settings
6.Adding a Payment Method
7.Adding Push Notification settings
8.Adding a Google Login option

1. Creating a New Configuration in Kuika for API Configuration
To create a new configuration, open the Configuration Manager view mode from within the project you are working on at platform.kuika.com. Select API from the Web UI, iOS, Android, and API options under the Create a new configuration heading in the Configuration Manager view mode. Name the configuration via the text input box that opens at the bottom and click the "CREATE" button.
IMG 01: Configuration Manager screenshot (Alt text: Configuration Manager Screen)
​
2. Adding Application Configuration Information for API Configuration
On the next screen, you must provide information to perform API Configuration.
IMG 02: API Configuration screenshot (Alt text: API Configuration screen)
To connect the application you have developed to the database, you must enter the database connection information via the "Database Connection String".
You can leave this blank to use the Database connection created by Kuika.
3. Adding an Authentication Provider for API Configuration
For the application you developed with Kuika, you can use the "Authentication" method that Kuika offers to users and is preferred by default, "Kuika Auth", or you can choose one of the various "Authentication Providers".
IMG 03: Screenshot of adding Authentication Provider configuration (Alt Text: Adding Authentication Provider configuration screen)
To select Authentication, click the drop-down menu opposite the Configuration heading under the "Authentication Provider" . You can select “Kuika Auth” in the drop-down menu or click “ADD NEW”.
IMG 04: Entering Authentication Provider Setting information on the pop-up that opens (Alt text: Authentication Provider Setting screen)
On the pop-up screen titled "Authentication Provider Setting", "Generic Auth(REST)" is selected by default as the authentication provider.
Click the drop-down menu next to “Type” to change the provider type. You can choose one of the “Generic Auth(REST)”, “oAuth 2.0”, “LDAP” and “MSAL” options in the drop-down menu.
After completing the selection process, fill in the necessary information for the relevant "Authentication Provider" and click the "CREATE" button.
4. API Configuration Adding Password Policy for API
After you have chosen "Kuika Auth" as the authentication provider in the application you have developed, you must add the password policies for your application. To do this, click the drop-down menu next to the “Configuration” heading under the “Password Policy” . Select the “ADD NEW” option in the drop-down menu.
IMG 05: Entering Password Policy Setting information on the pop-up that opens (Alt text: Password Policy Setting screen)
For the "Password Policy Setting" pop-up screen that opens, first name your password policy. You can choose the password policy criteria that you want to have in your application from the criteria in the "Character and Size" tab. These criteria are stated below:
Include lowercase letters(can be specified)
Include capital letters(can be specified)
Including digits(can be specified)
Include special characters(can be specified)
Not containing a specific word
No ordinal digits
Not containing sequential characters
not include birthday
No username or surname
Set minimum and maximum password length
IMG 06: Entering Locking information on the pop-up that opens (Alt text: Locking screen)
Then you can set the password lock criteria and new password setting criteria under the "Locking" tab. These criteria are stated below:
Password duration
Notification near password expiration
Setting the account lockout threshold
Reuse of the last password(s) used
After completing the criteria determination process, click the “CREATE” button to add your password policy.
You can leave this blank to use the password policies created by Kuika.
5. API Configuration Adding Email Settings for API
You can use SMTP or Amazon Web Server (AWS) alternatives for the "Mail Settings" in the application you developed. To use SMTP, click the drop-down menu opposite SMTP. Select the “ADD NEW” option in the drop-down menu.
IMG 07: Entering SMTP Setting information on the pop-up that opens (Alt text: SMTP Setting screen)
On the pop-up screen titled "SMTP Setting", fill in the requested information about your email server. After filling in the information, click the “CREATE” button to create the SMTP setting.
To use AWS, click the drop-down menu opposite AWS. Select the “ADD NEW” option in the drop-down menu.
IMG 08: Entering API AWS Setting information on the pop-up that opens (Alt text: AWS Setting screen)
On the pop-up screen titled “AWS Setting” that opens, fill in the requested information about the AWS account you have. After filling in the information, click the “CREATE” button to create the AWS setting.
6. Adding API Configuration Payment Method
In the application you developed with Kuika, you can quickly perform your payment methods through Stripe, an international payment method. To add a payment method using the Stripe integration, click the drop-down menu next to the “Stripe” heading under the “Payment Methods” . Select the “ADD NEW” option in the drop-down menu.
IMG 09: Entering Stripe Setting information on the pop-up that opens (Alt text: Stripe Setting screen)
On the pop-up screen titled "Stripe Setting", you need to add the information about your Stripe account. You can use the API Keys page in your Stripe account to access this information. You can access detailed information about creating a Stripe account and Stripe in our content titled "Stripe Integration".​
After filling in the information, click the “CREATE” button to create the Stripe setting.
7. Adding Push Notification Settings for API Configuration
"Push Notification" in mobile applications you developed with Kuika. To send a “Push Notification”, you must first make the necessary adjustments. You can adjust the settings for iOS and Android devices via the "Send Push Notification Settings" tab on the API Configuration page. To adjust the "Push Notification" settings for iOS devices, click the drop-down menu next to the "iOS" heading under the "Send Push Notification Settings". Select the “ADD NEW” option in the drop-down menu.
IMG 10: Entering Push Notification Setting information on the pop-up that opens (Alt text: Push Notification Setting screen)
You need to add the requested information on the pop-up screen titled "Push Notification Setting".
Name the Push Notification setting via the text input box next to the Name header. Next, enter your Team Id.
There are some steps you need to do to access your Team Id information. For Team Id, you must first sign in to the Apple developer center.​
Open the Account page by clicking the Account button and scroll down to the Membership Details on the page that opens.
"Team Id" information in the membership details section. Enter the Team Id information you have accessed in the relevant field in Kuika.
After providing the Team Id entry, the next step will be to specify the post type.
If you are going to provide the publication by sending the .ipa file to the simulator, you should select the publication type as "Development". If you are running the application via Testflight, you should choose "Production" as the broadcast type.
The last information you need to add on the Push Notification Setting screen for iOS is "Notification Certificate". To access the certificate file with the .p8 extension that you will use for iOS devices, you must follow some steps.
To get the P8 file, go to the Apple Account Manager page and log in with your Apple Developer account. Open the Users and Access Page after login.
Click the "Keys" button on the page that opens. You can create and download the.p8 file by clicking the “ +” icon on the “Keys” page that opens. Upload the downloaded file with the “Upload” button opposite the “Notification Certificate” and click the “CREATE” button.
You can only download the P8 file once. For this reason, you should keep the file well.

Click the drop-down menu next to the “Android” heading under the “Send Push Notification Settings” to set the “Push Notification” settings for Android devices. Select the “ADD NEW” option in the drop-down menu.
IMG 11: Entering Firebase Setting information on the pop-up that opens (Alt text: Firebase Setting screen)
You need to add the requested information on the pop-up screen titled "Firebase Setting".
Name the Firebase setting via the text input box next to the Name header.
Next, enter your Sender Id, Server Key, and Notification Certificate information. There are some steps you need to do to access this information.
First you need to sign in to the Firebase Console.​
Click on the relevant project from the Firebase Console home page. If you don't have a project created before, create a new one.​
Go to the settings page by clicking the "Gear" icon next to the "Project Overview" item in the left panel menu on the project screen that opens.
Download the file named “google-services.json” in the “General” tab. You will use this file as a "Notification Certificate".
Then click on the “Cloud Messaging” tab.
On the page that opens, you can find the Server Key and Sender Id information under the heading "Cloud Messaging API (Legacy)".
Now go back to Kuika. Fill in the Sender Id and Server Key information. Upload the file named “google-services.json” that you downloaded as Notification Certificate via the “UPLOAD” button.
“CREATE” button after completing the installation process.

8. Add Google Login Option for API Configuration
You can enable users to log in to the application you developed with Kuika using their Google accounts. To add a login option with Google, click the drop-down menu next to the “Google” heading under the “Other Login Options” . Select the “ADD NEW” option in the drop-down menu.
IMG 12: Entering Google Login Setting information on the pop-up that opens (Alt text: Google Login Setting screen
On the pop-up screen titled "Google Login Setting", you must enter the required information.
First, name the Google login setting.
Next, fill in the Client Id, Client Secret, Server Client ID, Server Client Secret, and iOS Url Scheme information. There are some steps you need to do to access this information.
First go to Google Console.
If you have not created a project on the Google Console before, click the Create Project button to create a new project.
After creating the project, click the CREATE CREDENTIALS button.
Create 3 “OAuth Client IDs” of “Web application”, “Android” and “iOS” types by clicking “OAuth Client ID” in the menu that opens.
You can find the "Client Id, Client Secret, Server Client ID, Server Client Secret and iOS Url Scheme" information in the 3 "OAuth Client IDs" you created.
Now go back to Kuika, add the information to the relevant fields and click the “CREATE” button.
After doing all these operations, click the "CREATE" button to create the API Configuration settings.
Last modified 12d ago