diff --git a/header-maven-plugin/pom.xml b/header-maven-plugin/pom.xml
index 06aaccbf26..78015d9253 100644
--- a/header-maven-plugin/pom.xml
+++ b/header-maven-plugin/pom.xml
@@ -50,7 +50,7 @@
maven-plugin-plugin
3.4
- header-maven-plugin
+ header
true
diff --git a/server_admin/topics/clients/saml/idp-initiated-login.adoc b/server_admin/topics/clients/saml/idp-initiated-login.adoc
index ccaca52d28..0a001127f8 100644
--- a/server_admin/topics/clients/saml/idp-initiated-login.adoc
+++ b/server_admin/topics/clients/saml/idp-initiated-login.adoc
@@ -6,7 +6,7 @@ In the `Settings` tab for your client, you need to specify the `IDP Initiated SS
This is a simple string with no whitespace in it.
After this you can reference your client at the following URL: `root/auth/realms/{realm}/protocol/saml/clients/{url-name}`
-The IDP initiated login implementation prefers _POST_ over _REDIRECT_ binding (check <> for more information).
+The IDP initiated login implementation prefers _POST_ over _REDIRECT_ binding (check <<_saml, saml bindings>> for more information).
Therefore the final binding and SP URL are selected in the following way:
1. If the specific `Assertion Consumer Service POST Binding URL` is defined (inside `Fine Grain SAML Endpoint Configuration` section
diff --git a/server_development/pom.xml b/server_development/pom.xml
index 0ec8ac3e64..30d965d75b 100644
--- a/server_development/pom.xml
+++ b/server_development/pom.xml
@@ -11,7 +11,7 @@
Server Developer
server-development
- jar
+ pom