# Phoenix 1.6.0 Released **URL:** \ **Category:** Backend Chat/Discussions\ **Tags:** elixir, framework-release-news, phoenix\ **Created:** [30 September 2021 23:18 UTC](https://forum.devtalk.com/t/phoenix-1-6-0-released/23355 "2021-09-30T23:18:25Z")\ **Posts on this page:** 1\ **Showing post:** 13
**Author:** ![OvermindDL1](https://forum.devtalk.com/user_avatar/forum.devtalk.com/overminddl1/32/52_2.png) [@OvermindDL1](https://forum.devtalk.com/u/OvermindDL1)\ **Post date:** [1 October 2021 21:21 UTC](https://forum.devtalk.com/t/phoenix-1-6-0-released/23355/13 "2021-10-01T21:21:37Z")
> [@Cellane](#): > > Hmm… I can see the argument for wanting to have a nice and clean integration with third-party auth services, but I’m really not sure if I’d ever want something that big, potentially brittle (services may and will go down eventually, protocols might change over time) and reliant by nature on services outside of your sphere of influence in the core of the framework… (Edit: I mean, exactly trying to get rid of things that the Phoenix team can’t easily fix on their own is one of the reasons to get rid of their prior Node.js/WebPack integration, so…) The reason why local auth should not be used in many-faceted, but that doesn’t mean you have to use someone else. I host my own OIDC server for my services (which it itself also has a local login, or other auth to github, google, and a few others), that’s fine, but it should _not_ be in the webapp itself, that’s not its job at the very basic. * * * Side topic, It’s interesting how much their new HTML-eex engine is copying even more of what Drab did years ago (though it looks like it’s missing some abilities that drab had like fast in-place identification and replacement for the live swaps)… Still irritated about all that… \>.\> --- _[View the full topic](https://forum.devtalk.com/t/phoenix-1-6-0-released/23355)._