Some examples lead to errors in FreeRADIUS

By commenting out the examples, FreeRADIUS does not complain any more about
unknown Mappings/Attributes.
Also added a Changelog

Fixes #33, #35

Changelog

@@ -0,0 +1,32 @@
+Version 3.1, 2019-05-17
+
+  * Fix mods-perl-privacyidea module for FreeRADIUS 2 (#29)
+  * Fix package dependency with RHEL7 (#25)
+  * The simple "decode_json" does not work under 18.04
+  * Add template for mods-perl (#11)
+  * Provide config for packing for FreeRADIUS2 and 3 (#11)
+  * Add time measurement for privacyIDEA API call
+  * Use the generic subdir from JSON response (#12)
+  * the auth module returns RLM_MODULE_NOTFOUND (#19)
+
+Version 3.0, 2019-03-22
+
+  * Add build environment for ubuntu (#17)
+  * Return RLM_MODULE_FAIL if return codes is not OK 200 (#15)
+  * Add a configuration option for fixing null byte (#13)
+  * Allow several mapping rules for one radius Attribute
+  * Add prefix and suffix to RADIUS attribute
+  * Allow to map substrings of user attributes to RADIUS values (#8/#9)
+  * Pass any RADIUS attribute as client to priacyIDEA (#7)
+  * Add a configurable request timeout
+  * Add support for proxy from environment variable (#2)
+  * Add arbitrary RADIUS attributes in the response.
+  * Add user-agent to request (#1)
+  * Add readme
+  * Add privacyIDEA-Serial to RADIUS response
+  * Add freeradius module configuration to /etc/privacyidea
+  * Add accounting module to FreeRADIUS config.
+  * Improve REALM handling in RADIUS plugin
+  * Fix some FreeRADIUS/SSL issues.
+  * Improve the debian packaging.
+  * Added RADIUS support

rlm_perl.ini

@@ -11,43 +11,47 @@ serial = privacyIDEA-Serial
 [Mapping user]
 # The Mapping is used to add attributes to the RADIUS response.
 # The value is read from the privacyIDEA response.
-# In this case the content of the privacyIDEA response 
+# In this case the content of the privacyIDEA response
 #   detail->user->group
 # will be written to the RADIUS response attribute "Class".
-group = Class
+#
+#group = Class
 
 [Attribute Filter-Id]
 # With the multivalue attributes in the user response of privacyIDEA
 # we can also do an attribute mangling.
-# privacyIDEA may return a value like 
+# privacyIDEA may return a value like
 #   detail : { user : { acl : ["CN=vpn-user,ou=sales,dc=example,dc=com",
 #                                   "CN=domain users,ou=sales,dc=example,dc=com"]}}}
 #
-# The below example would match the privacyIDEA userAttribute "acl" and check if the 
+# The below example would match the privacyIDEA userAttribute "acl" and check if the
 # value matches the regex. If it does, it will add the substring $1 as the
 # "Filter-Id" to the RADIUS response.
 # The ini file can contain several "Attribute" groups, to add several RADIUS attributes
 # to the response.
-dir = user
-userAttribute = acl
-regex = CN=(\w*)-users,OU=sales,DC=example,DC=com
-prefix =
-suffix =
+#
+#dir = user
+#userAttribute = acl
+#regex = CN=(\w*)-users,OU=sales,DC=example,DC=com
+#prefix =
+#suffix =
 
 [Attribute otherAttribute]
 # If you want to have more mapping rules for a RADIUS attribute you
 # can give the section an arbitrary name and use the key "radiusAttribute".
 #
 # This example will set the Filter-Id to "FIXEDValue" if the user is located in
 # resolver1.
-radiusAttribute = Filter-Id
-userAttribute = user-resolver
-regex = resolver1
-prefix = FIXEDValue
+#
+#radiusAttribute = Filter-Id
+#userAttribute = user-resolver
+#regex = resolver1
+#prefix = FIXEDValue
 
 [Attribute Class]
 # This example will add the RADIUS Attribute Class = SomeOtherValue
 # if the user is in the resolver "myResolverName".
-userAttribute = user-resolver
-regex = myResolverName
-prefix = SomeOtherValue
+#
+#userAttribute = user-resolver
+#regex = myResolverName
+#prefix = SomeOtherValue