New Requirement:Want to send email containing only the ticket id of the issue newly created to the client who raised the issue.How can I proceed with this requirement?Please help me out.
Thanks in advance
Related
I want to send an email to the registered user once the admin creates a new user saying that " the user successfully registered with the xyz email id.. " Is there any option to achieve this in keycloak 19.03 or above ?
Or Is it an out of box option in keycloak ?
Currently on initial login attempt, the newly created users can opt for forgot password and they will get a password reset link, through which them can login and verify their email. But welcome mail is possible ?
Any help is greatly appreciated !!
This is not an out of the box feature from Keycloak, but can be easily extended.
Step 1: Update your realm to record the events, show in below image.
Step 2: Extend the Event listener API from keycloak. You can find official guide here -> https://www.keycloak.org/docs/latest/server_development/#_events
Listen to user registration events and send appropriate emails.
I got the following error when login into sonarqube.com:
You're not authorized to access this page. Please contact the administrator.
Reason : You can't sign up because email 'abc#abc.com' is already used by an existing user. This means that you probably already registered with another account.
It seems the issue is that the github handle of the above account got changed as some point!
Please use about.sonarqube.com/contact in order to contact administrator of sonarqube.com
We are using GitHub Enterprise 2.5.1.
In our company, when a user switches to a new role, a new AD account will be created for him, with a new set of permissions. e.g. my current account is "huj" as a developer with email address "Jirong_Hu#otpp.com, if I become a BA, then:
The old account "huj" will be marked as "OIM Deletion" in AD.
A new account called "huj2" will be created for me, with the same old email address, Jirong_Hu#otpp.com.
My questions are:
As account is automatically created upon login, if I login to GitHub with the new account "huj2", I got this error: Unable to create the user because email Jirong_Hu#otpp.com is already taken and emails is invalid.
How can I create the new account "huj2" in GitHub, with the same old email address.
What's the consequence of doing the above?
I know this is an old post but it still shows at the top on a Google search on this subject.
Some email providers support using special characters to use multiple email addresses that map to a single account.
For example, if you use Gmail and your email address is myemail#gmail.com and you already have an account on GitHub with that email you can create a new GitHub account using myemail+1#gmail.com
The simple answer is NO.
You can't create more than 1 ID in GitHub by the same email, but you can do it by using multiple email IDs.
If you try to do it, GitHub will show an error - "email invalid or already taken", so delete the present account or make it with a new email id .
There are two ways to resolve this issue:
If the existing user has no activity, then delete this existing account.
Otherwise change his email to something else, then when the new user logs in, a new account will be created.
I am using a custom Parse server hosted on Heroku.
My overall goal is for a unique PFUser to be created through someone clicking a button or a activation link in an email.
I have figured out how to send emails using Send Grid, however I have no idea how to make a custom button or link in the email that will execute some unique code.
My ideal work flow is:
User inputs unique username and password then clicks sign up
An email is sent to the users email with a button or a link
Once they click the button or link, somehow unique code is executed which signs up a new PFUser using the username and password that the user originally inputed.
I know how to do the first two steps, but have no idea how to execute the unique code from an email.
How is executing unique code from an email usually done? I have read something about tokens being used?
Could someone please outline for me how this process works and where I can go to learn all about executing unique code from emails?
Thanks, I appreciate all the help!
Code is never executed from email because it is a severe security risk.
To implement something like you're describing, you would send an email to the new user with a unique link to a web page like http://yoursite.com/confirmation/?id=some_unique_id_like_a_UUID
Then on you write the web page (at http://yoursite.com/confirmation/) to read that id value and then do the action that "signs up a new PFUser using the username and password that the user originally inputed."
I'm having trouble to achieve this. What I would like to do is be able to edit the content (description) of an email entity for a qucik campaign before it's sent (or after it's created).
I've tried many different plugins registration without much luck.
Prevalidate Create Email : this one fires ok but only when a user creates and save the email. when the email is created by the quick campaign it is not triggered.
Prevalidate Send Email : this one fires only for when a single email is sent by a user action and does not allow to modify the description anywa
Prevalidate BackgroundSend Email: this one is correctly triggered when the emails created by a quick campaign are sent, but it does not let me modify the description.
Anyone has done that before ?
I'm using CRM 2011 online.
Any help would be greatly appreciated.
Regards
Found the solution which is to simply use the plugin on Create Email Pre-Operation instead of Pre-Validation like I was doing.
For some reasons, the Pre-Validation doesn't trigger when emails are created in the background.