shankardevy
Best Practices for Oban jobs with sensitive information
What is the recommended approach to send emails that contains sensitive information through Oban jobs? Like for eg., sending OTP which is stored in the db in the hashed format and shouldn’t stored in plain text format? The job perform function cannot query this data from the db as it’s already hashed and if the OTP is present in the serialised job data, it will persist in the DB as plain text which in this case is not desired.
Marked As Solved
sorentwo
This seems to be solved, but I’d like to note for future readers that there is an encrypted jobs option in Oban Pro for instances when sensitive data must be put in the database.
Also Liked
NobbZ
Generate the OTP as part of the job, not when creating the job.
This way the job has control over the clear and hashed version of the OTP.
You probably do not need the OTP before it has been sent to the other party anyway.
ibarch
Is it possible to generate, send and store hashed OTP inside the job?
NobbZ
Please give ibarch the credit, as it is their suggestion but with more words.
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance









