From 9003f7f557c5e947b2dfe9b55388d252a31f43a6 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Mon, 2 Jul 2018 07:41:20 +0200 Subject: [PATCH] highlight a imported point --- website/blog/2018-07-02-trying-new-auth.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/blog/2018-07-02-trying-new-auth.md b/website/blog/2018-07-02-trying-new-auth.md index b783ea7b..c1b01a42 100644 --- a/website/blog/2018-07-02-trying-new-auth.md +++ b/website/blog/2018-07-02-trying-new-auth.md @@ -14,7 +14,7 @@ For Home Assistant 0.73, I've sprinted together with [@awarecan] to ensure that - If you opt-in for the new system, the API password will no longer work. - To not force a hard break with the ecosystem around Home Assistant, a temporary legacy mode has been added to turn API password support back on. This will be removed in the future. -The system is not yet ready for mainstream consumption, we still need to add Hass.io support and a user interface to help guiding the user to create their first user account and to manage users. You can follow (and join!) the work to be done [here](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3Aauth). +**The system is not yet ready for mainstream consumption**, we still need to add Hass.io support and a user interface to help guiding the user to create their first user account and to manage users. You can follow (and join!) the work to be done [here](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3Aauth). If you're interested in trying it out, keep on reading.