apoorv-2204
To login in our custom crm, We do SSO from google, for specific email domain,. Its achieved via a workos.
I want to implement a feature where I can logout a user based on the email. Say, I go to admin setting, for the user and click on logout, so he/she get logout from CRM.
How can I get session for that person. and clear his session. like this
the_conn_based_on his email id |> clear_session() |> configure_session( drop: true)
Is it possible to do in phoenix or I have to look into workos?
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
LostKobrakai
Unless you’re using a server side session store there’s no way to drop a session from the server side. The default session store is cookie based. You have no control over the cookie (on the client).
Depending on the system used for authentication you could however still for the user to be logged out on their next request. E.g.
mix phx.gen.authstores valid user token in the db, which you can remove to invalidate a users logged in status. This would indirectly cause the session to be dropped as well.apoorv-2204
I am not soo much aware of dealing with session in phoenix.
But we get a profile code in the callback and we fetch details from provider,and put in session. then just do Conn|> configure_session(renew: true)
apoorv-2204
So I have to impl Plug.Session.Store behaviour , where operation are on db and just mention the module name in session options?
@session_options [
# Authentication lasts only 3hours
store: :session_store_module,
]
adw632
Also take care to log the user out of any liveviews and channels when you revoke the session : Security considerations — Phoenix LiveView v1.2.5