OIM _oracle identity manager when all the jobs run user will be provisioned to oim as well as OID. After user creation welcome email automatically send to the user. Some of the users like manager role only have the mail id. All other users welcome mail send to their manager. The managers will share the details to the users.
Now my requirement is the welcome email need to be copied to one of the default mail id. Could you please suggest me something. It's a task provided from my client. I need the help from OIM support side
Related
I am working in a team, I am admin of Azure devops, and I have a requirement, I want to send a email notification of every pull request created by my developers team.
But problem is that my all developers don't have email domain access in my client's Azure devops.
My mean is my client name for example is ABC so being admin client given me access by giving email id with admin authorization ashishjain#abc.com but developers don't have this mail domains (because we are vendors and working for client). In addition my client don't use full features of office 365.
Challenge is, how can i send a mail notification of every pull request using my client's Azure devops to my developers who don't have mail IDs like abc.com.
When you create a notification you can specify the email address (any email address):
What kind of mail ID do they have to access your Azure DevOps? Even though different from #abc.com, such as xx#123.com, they should also be able to access their own E-mail xx#123.com
To be honestly, your requirement sounds like a little weird. According to your description, every pull request created by my developers team. These users should already been team members in your org.
You just need to Manage notifications for a team or group in your project. For example:
Team preference: use the team's default delivery preference.
Learn how to manage delivery settings.
If those develops are also not able to access their own sign-in E-mail address system. They cloud change their preferred email address for notifications.
You can change your preferred email address for notifications from
your organization preferences profile page. Notifications are sent
by default to the preferred email address for your organization
profile. This is typically the email address you signed into Azure
DevOps Services with.
Besides, you could also set any Custom email address: recipient is the specified email address in delivery options of your team notification.
Lastly, the E-mail which sent to develops notifications will not be the one who created the subscription. It hands by Azure DevOps Server.
I have a web application that allows registration and authentication through Facebook, Google and Windows Live. Each OAuth request has the required scope to retrieve associated e-mail addresses from the authentication provider.
The current situation is that an account is created based on the provider and the provided identifier. This means that if a user has logged in with multiple providers the user will have multiple accounts on the web application.
I want to have the ideal situation of having a single acccount even when using multiple providers. I was thinking about using the e-mail addresses to see if an account exists for the user. If it exists, use the account based on the e-mail address.
How safe/reliable is this? Do all OAuth providers mentioned validate e-mail addresses? Better ways?
EDIT: Ran a tests and came up with this. Still looking for further advice :)
FaceBook: Cannot authenticate with unvalidated e-mail. Additional e-mail will not appear until validated.
Google: Provides `verified_email`. Additional e-mail will not appear until validated.
Windows Live: Cannot authenticate with unvalidated e-mail. Additional e-mail will not appear until validated.
Interesting question. You could try to use e-mail to check if user exists, but the problem is, user could be using different e-mail addresses for different providers.
My suggestion would be asking user (once he/she logs into your application using one of the methods) to attach other providers to to this account, so he/she can use them as well to log into your application.
It doesn't completely solve your problem (I'm not sure if solution exists), but user will have more control that way and you'll reduce the amount of accounts per user.
I've a domain and I've successfully configured Email service via Google Apps.
I've created 5 email accounts too.
Now I want to track all the incoming/ outgoing emails.
Is there any way, if any person(among those 5 persons), sends or receives an email, I want a copy of that email in my inbox too automatically.
Thanks in advance.
You can use GAM and Audit monitors to get a copy of a users mail sent and received. You'll also see Chats and Draft messages with an email monitor:
http://code.google.com/p/google-apps-manager/wiki/ExamplesAccountAuditing#Create_a_Audit_Monitor
This feature requires Google Apps for Business or Education.
Jay
I am not sure you can receive a copy in another account but you can configure each of the accounts to delegate access to your account so that you can view their sent/received messages. It is more manual than you would like however.
http://support.google.com/mail/bin/answer.py?hl=en&answer=138350
The best way to do that with out going into the GAM and use the audit, is to configure mail forwarding for each email by going into the gmail account interface.
Another solution that can be used, is to create an external gmail email, and use the google apps email routing to send all the emails to the external one.
On the external one you can just do what ever you want with the email, such as filtering by receiver and forwarding it to your selected destination.
Hope my answer helped a bit.
In our SaaS application each company (tenant) is given their custom domain like companyName.ourapp.com
We would like to provide some email services like:
Ability to send and receive email notifications from info#companyName.ourapp.com and similar addresses
Ability to create new email accounts in clients' subdamains at runtime, programmatically, when needed. For example we would have separate emails created for each "opening" so that emails sent to this address would be parsed info would be extracted
Similar tasks
For now I just don't even know on where to look and how this could possibly work.
As far as I understand email it should be some kind of custom mail server (SMTP) serving all sub-domains and having API we can use to send emails, list and retrieve messages etc.
Please suggest how it may work and is there any components out there we can use to implement this.
There are three options for this.
Create an email server and programatically configure it to accept or deny the specific accounts. Then use cron to poll via pop3 or imap and download the messages for the account. You can then send them on for the customer or handle them in your web app.
Create a script that is fired by the email server as it receives each email. The script can then handle what to do with the email as it's received.
Use a third party to receive the email via HTTP Post at your app. Using CloudMailin for example would allow you to create a custom authorization filter that would call your app in realtime and determine if the given account exists and messages should be accepted for it.
I wrote a blog post for Rails about receiving incoming email, however the principals would apply to any programming language and framework.
my question is about the workflow of a web registration.
1) register with email + basic data
2) activate the account with a special secret link <- is this necessary?
3) allow the user to log in to the system
EDIT: I want to make the process as simple as possible without a password to choose/remember.
In more detail:
After a user is registering on a web site I sent out a confirmation with a generated password to login on the site and proceed.
Many sites sent an activation link first and then allow logging in to the system.
Is there any reason to do this additional step when I generate the password and sent it out to the user?
Thanks for your answers.
Is there any reason to do this additional step when I generate the password and sent it out to the user?
To ensure that the provided email address exists, and belongs to the person who registered the account.
I've noticed an increasing number of websites which skip this step. It seems to be a trend.
The purpose of the activation link is to guarentee that the email address provided by the user is one to which they have access. If you are generating a password and sending it via email to the user's email address, then the link is not required (because them logging in means that they read your email).
However, email is generally not a secure way to distribute information over the internet. You are sending them the password in plaintext, and you do not know how many people have access to that email account (e.g. a shared family account). I think you would be better off allowing the user to choose their own password at registration and then send them a link (offer to generate a password for them on the registration page, if you really believe that generating it is better).
The validation of an email account is usually to help prevent someone creating numerous accounts. This helps prevents spammers and various other bad people from attacking your site from different accounts.
In general you're trying to ensure that the person is who they say they are and that you have an outside means of communicating with them.
1 - to ensure that the email is belong to the registerd user.
2 - to make it harder to the people want to create many accounts (like forums where a single person have so many accounts to use them in voting or somthing).
I remembered a funny site that gives you a 10 minutes email , just to skip the process of creating a new email or even spamming your email by the sites you've registered in.
This way you make sure that the email address is valid and it will be more difficult for a spider to generate many users than without this step. Also, you might do a lot of things in your database when a user is registered and you can do these after the user is validated, to save time by not creating extra traffic on your database server for fake users.