nit

Author: leifj

example/plugins/microservices/attribute_authz.yaml.example

@@ -4,7 +4,7 @@ config:
     attribute_allow:
         target_provider1:
             requester1:
-                attr1: 
+                attr1:
                    - "^foo:bar$"
                    - "^kaka$"
             default:

src/satosa/micro_services/attribute_authorization.py

@@ -40,10 +40,10 @@ class AttributeAuthorization(ResponseMicroService):
 
 The use of "" and 'default' is synonymous. Attribute rules are not overloaded
 or inherited. For instance a response from "provider2" would only be allowed
-through if the eppn attribute had all values containing an '@' (something 
+through if the eppn attribute had all values containing an '@' (something
 perhaps best implemented via an allow rule in practice). Responses from
 target_provider1 bound for requester1 would be allowed through only if attr1
-contained foo:bar or kaka. Note that attribute filters (the leaves of the 
+contained foo:bar or kaka. Note that attribute filters (the leaves of the
 structure above) are ORed together - i.e any attribute match is sufficient.
     """