lardcanoe
I am using ash_auth for password/google registration/signup.
I was looking into also using it to let a user connect to a 3rd party service so I can track tokens, but I do NOT want to enable registration or signup for that.
This doesn’t seem to be a use case that ash auth currently allows. True? I should just use assent directly?
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
Hi everyone,
I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding.
I sta...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
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
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted”
Version...
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
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
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
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
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
- #metaprogramming
- #hex
- #security











Showing Posts 1 to 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
zachdaniel
While it might be possible to make that work, I know that it was not designed/tested for that kind of use case. I think a case could be made that it can/should be added to
ash_auth, but for now I’d assume it’s not on the table. Perhaps open an issue on the repo to track that as a feature request? I imagine that if I or @jimsynz want to do something similar that we’re going to want to reuse all the goodies in AshAuthentication instead of hand rolling it from scratch.PRs welcome for this kind of feature, although want to run it by @jimsynz as well
jimsynz
I think you’re right @zachdaniel - it’s authentication adjacent so not really something I had considered. However, if you set up registration for this 3rd party service (let’s call it “guthib”) you can modify the
register_with_guthibcreate action to only work if the user already exists. That way you can still utilise the identity resource to keep track of their tokens and keep them fresh. It is a bit of a hack, and you’d have to manually implement your sign in UI so that it didn’t provide the guthib option to your users. I would welcome a PR that adds the ability to add identities to authenticated users.Good luck!
lardcanoe
It dawned on me after a bit of tinkering that ash_auth wasn’t gonna be the right approach anyway for me. I have a model where a User can be part of multiple Organizations, and I need to tie the refresh_tokens to a UserOrg, not a User. That was going to mean I would need to have the UserOrg also be an identity for ash_auth, which just wasn’t right (since I would be forced to define a strategy).
Ultimately,
assentwas like ~30 lines of code spread across the router, controller, and a tiny OAuth module. (Plus a new resource to store the tokens).Thank you for the feedback!
jimsynz
Glad you found a solution that works for you!
ajst7les
@jimsynz I was wondering if this was on the roadmap?