I have changed the signup process is in existing social engine signup process is three-step (Create Account, Personal Information, Photo).
But as per my project requirement made changes is show only step-1.
My problem is Email verification email is not sending after a click on step-1 submit button.
When I follow the three-step signup process then Email verification mail is sending properly.
SocialEngine Version: 4.10
Related
We are using Congnito hosted and users are clicking the "Forgot Password" option, entering their email which does not exist as a user, but then still being told to check their email for a reset code that never appears.
Is there any ways to change the messaging or send an email with instructions on creating a new account?
I currently have it so that when a root user adds a new user to group(via email), it will send a message to their inbox with a link to create a password on the web page. However, do not know how to create a link that will send them to a registration page on my Flutter web app after they click on it in their email. Any ideas?
We have created a Cumulocity solution and created a very clean, simple interface for our users. We also offer a 'Change Password' feature to the solution users.
Changing the password in Cumulocity causes an email to be sent to the user containing a link for the user to follow and enter a new password. The issue is that the link always navigates the user to the built-in Cumulocity UI - this breaks the consistency of the user experience!
Is there a way we can create this password reset capability but have the email link direct the users to a customised UI to enter their new password?
The following should work:
The content of the password reset email can be configured on system level. Mention just the host there, not a particular app ({host}?token={token}).
Set your custom app to be the default app for the tenant. That will make sure that the user gets to your app when they click on the link.
Note: If you change the default app for a tenant, you may need to clean your browser cache to actually see the new default app.
To make the experience for our users more convenient we implemented a feature with allowed a user to automatically get logged in when he clicks on a link he received via email.
In the past he had to click on the link and then had to enter his password. By providing a special security token in the link, we can now automatically login the user without the need for entering his password.
A few days after we went live with this feature, internal pages (which can only be accessed via password or via the special email link) appeared in the google search results. We are using Gmail as a Email provider for sending emails from our system.
The only explanation I have for this behaviour is, that google is crawling the links in the emails. Which is not very nice from them if those are "private" links.
Is there a safe way to still allow users to login without password via a special link they receive in their email, without google being able to crawl the internal pages?
I am trying to create a sample test application that authenticates a user wearing Google Glass.
I have read the following page
https://developers.google.com/glass/develop/gdk/authentication
I need to know how will the authentication actually work. Now lets say I have an app "XYZ" uploaded onto MyGlass. User turns on the app via MyGlass and then automatically gets redirected to a web page say, for example,
http://www.example.com/glass/authenticate.html
In this web page, he has to sign in using a username and password. Once he clicks submit will he be redirected to another webpage on the browser or will the Glass application get activated. Where will the userToken be obtained. Will it be on Glass?
I am really confused. Please can someone help me out.
What exactly is the flow for authentication on Glass?
Assuming you're doing 3rd part authentication (i.e. your own users, not google accounts).
Once you click Submit on your login page:
Server-side: If the user is valid, call the Mirror API to insert the account, including your authToken and the userToken. The userToken will be a query parameter added to your login url by the glassware store.
Close the page using window.close(). The Glassware will then be installed on the user's device.
When the user launches your glassware, retrieve the account from the Mirror API, and then retrieve the authToken that you inserted in step 1. for that particular account.