Using Sign in with Apple allows users to create an account in the INETAPP server using their existing Apple ID. Users will get a seamless login experience using native dialogs on Apple devices, using the Safari browser. Due to Apple's focus on privacy and security, users can be sure, that their data is transmitted and verified in the most secure way. Users can also leverage the private email relay service using Sign in with Apple.
The configuration of the login provider requires an Apple Developer account, the enrollment in the Apple Developer Program, as well as the following:
The configuration will ask for the following information:
The Application ID with the capability Sign in with Apple is required to tie the private key and team together. To create a new Application ID, follow the steps:
(+)
at the titlecom.mycompany.oauth
By clicking continue, you will now create a new Application ID, enabled with Sign in with Apple. Later-on you may edit this App ID, or any other, to modify the capabilities.
The Service ID will be used as client_id
during the authorization of your users. To create the Service ID, please follow the steps:
(+)
at the title.client_id
.client_id
is a publicly known string which will be visible in the browser during redirection to Apple's sign-in servers.To finish the registration, select Continue and then Register.
The Private Key, when created, consists of two parts of information that are required in the INETAPP configuration: the Key ID and the Private Key itself. The Key ID is the name, generated by Apple, for your Key. The Private Key is a file that you will download after it was generated. You have to upload the file to the INETAPP server, where it is stored securely in the file persistence.
To create the Private Key, please follow the steps:
(+)
at the titleNow, during key creation, you will be offered to download the Private Key. This is critical as it will not be displayed again after being downloaded. Also, the screen shows the Key ID which you have to use in the INETAPP configuration. Please store both, the Key ID and the Private Key in a secure location. It will be used to verify authenticated users.