- Dynamic Role Assignment: Automatic role assignment can be made based on user information returned from Google (email extension, domain, etc.). For example, the ‘Admin’ role can be assigned to emails with the @kuika.com domain.
- Post-Login Redirection: Different screens can be displayed to users based on their roles after login. For example, separate panels for students and teachers.
- User Information Matching: Information from Google accounts (name, surname, email) can be matched with user profiles in the system and records can be updated.
Technical Risks and Precautions
- Google API Configuration: The Kuika application must be registered on Google Developers Console, and fields such as Client ID, Client Secret, and Redirect URI must be defined correctly.
- Unauthorised Access Control: Users who log in via their Google account should be granted access if they have an authorised role in the system. Otherwise, access should be restricted.
- Matching Issue on First Login: If the user information returned from Google does not match the user record in the system, synchronisation issues may occur. Email should be the most commonly used field for matching.
Sign In With Google is a user-friendly login method that allows users to access applications in a modern and fast way. It provides secure login with Google authentication, improving the user experience and eliminating problems such as forgotten passwords. Thanks to its web and mobile compatibility, it can be easily used on any platform, offering a powerful solution for accelerating user acquisition and increasing security for applications.
