diff --git a/CHANGELOG.md b/CHANGELOG.md
index b2c06dac..4ea8e29a 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,6 +4,11 @@ All notable changes to the INCORE documents generated by Sphinx package will be
The format is based on [Keep a Changelog](http://keepachangelog.com/)
and this project adheres to [Semantic Versioning](http://semver.org/).
+## [Unreleased]
+
+### Changed
+- Account instructions for registering with keycloak [#559](https://github.com/IN-CORE/incore-docs/issues/416)
+
## [4.12.0] - 2024-06-12
diff --git a/manual_jb/content/account.md b/manual_jb/content/account.md
index b633a2b9..2da166d8 100644
--- a/manual_jb/content/account.md
+++ b/manual_jb/content/account.md
@@ -1,15 +1,15 @@
# IN-CORE Account
-Access to the **IN-CORE** service requires a user account provided and operated by the [NCSA](http://www.ncsa.illinois.edu/) identity management system.
-Registering for an account is free and open to everyone. This account gives you access to all of the public data on
-the system and allows you to create data that is only accessible by you. If applicable, it is recommended
-that you sign up with your institutional email. To register for an account, please go to:
+Access to the **IN-CORE** service requires a user account. Registering for an account is free and open to everyone.
+This account gives you access to all of the public data on the system and allows you to create data that is only
+accessible by you. If applicable, it is recommended that you sign up with your institutional email.
+To register for an account, please go to:
-[https://identity.ncsa.illinois.edu/register/BSKC2UKQPU](https://identity.ncsa.illinois.edu/register/BSKC2UKQPU)
+[https://incore.ncsa.illinois.edu/auth/realms/In-core/login-actions/registration?
+client_id=react-auth](https://incore.ncsa.illinois.edu/auth/realms/In-core/login-actions/registration?client_id=react-auth)
-![IN-CORE login window](images/register.jpg)
+![IN-CORE login window](images/register.png)
+
+After you register, you will receive an email to finish your registration process. Once this is complete, an
+administrator will need to activate your account before you can access IN-CORE.
-After you register, you will receive an email to finish your registration process.
-It requires you to use 2 Factor Authentication (2FA) using Duo for making sure that you are not a bot.
-The 2FA is only needed during registration and when changing passwords, it's not required when logging
-in to IN-CORE services or to use pyIncore.
\ No newline at end of file
diff --git a/manual_jb/content/faq.md b/manual_jb/content/faq.md
index 365c2473..2e3dae8f 100644
--- a/manual_jb/content/faq.md
+++ b/manual_jb/content/faq.md
@@ -4,13 +4,11 @@
* *I want to try your IN-CORE services. Do I need to register?*
- A user must have an account [registered](https://identity.ncsa.illinois.edu/register/BSKC2UKQPU) with NCSA IN-CORE service. User credentials are required
- in accessing repositories such as hazard, fragility, restoration, geographic and other data sets.
- They are also used for accessing documentation server and Jupyter Notebook files.
+ A user must have an account [registered](https://incore.ncsa.illinois.edu/auth/realms/In-core/login-actions/registration?client_id=react-auth`) with NCSA's IN-CORE service.
+ User credentials are required for accessing repositories such as hazard, fragility, restoration, geographic and
+ other data sets. They are also used for accessing IN-CORE when running example Jupyter Notebook files.
- The username/password you chose during registration process in IN-CORE system is called
- LDAP password, based on specific Lightweight Directory Access Protocol authentication.
- You can test your registration credentials by accessing the [documentation server](http://incore.ncsa.illinois.edu/).
+ You can test your registration credentials by accessing [IN-CORE](http://incore.ncsa.illinois.edu/).
diff --git a/manual_jb/content/images/register.jpg b/manual_jb/content/images/register.jpg
deleted file mode 100644
index fcc78df0..00000000
Binary files a/manual_jb/content/images/register.jpg and /dev/null differ
diff --git a/manual_jb/content/images/register.png b/manual_jb/content/images/register.png
new file mode 100644
index 00000000..bc320340
Binary files /dev/null and b/manual_jb/content/images/register.png differ