Update Credits, package.json and roadmap

CREDITS

@@ -4,22 +4,28 @@
 
 Jason Fox <jason-fox>
 
-Javier Cerviño <jcague>
-
 Alejandro Pozo Huertas <apozohue10>
 
+Javier Cerviño <jcague>
+
 Cyril Dangerville <cdanger>
 
-<pmverdugo>
+iaoiui <iaoiui>
+
+pmverdugo <pmverdugo>
 
 Fernando López Aguilar <flopezag>
 
+K4s14 <K4s14>
+
+Abraham Peña <abrahamSecmotic>
+
 Federico Fernández <federicofdez>
 
-iot@ics <UniSurreyIoT>
+Kazuhito Suda <fisuda>
 
-jaKa <jkmcnk>
+fiware-austria <fiware-austria>
 
-Koen Karsten <koenkarsten>
+Gabriela <gabicavalcante>
 
-Gabriela <I-am-Gabi>
+Koen Karsten <koenkarsten>

package.json

@@ -1,6 +1,6 @@
 {
   "name": "fiware-pep-proxy",
-  "version": "7.8.0",
+  "version": "7.8.1",
   "license": "MIT",
   "description": "PEP oauth2 authentication proxy for FIWARE GE services",
   "author": "GING DIT UPM",

roadmap.md

@@ -18,15 +18,18 @@ the product:
 
 -   There are no new features planned for the next release.
 
+-   OpenID Connect: Keyrock GE will implement support to OpenID Connect for creating _id_tokens_. Wilma will support
+    these tokens for validating users identity.
+
 ## Medium term
 
 The following list of features are planned to be addressed in the medium term, typically within the subsequent
 release(s) generated in the next 9 months after next planned release:
 
 -   Unit tests: to be run in CI
 
--   OpenID Connect: Keyrock GE will implement support to OpenID Connect for creating _id_tokens_. Wilma will support
-    these tokens for validating users identity.
+-   COAP compatibility: supporting this protocol as an alternative of HTTP could improve the performance of IoT devices
+    authentication process.
 
 -   Integration with Context Broker Service Path: to support a better integration of authorization mechanisms with
     Context Broker, requests will take into account the CB service path in HTTP headers.
@@ -37,8 +40,5 @@ The following list of features are proposals regarding the longer-term evolution
 of these features has not yet been scheduled for a release in the near future. Please feel free to contact us if you
 wish to get involved in the implementation or influence the roadmap
 
--   COAP compatibility: supporting this protocol as an alternative of HTTP could improve the performance of IoT devices
-    authentication process.
-
 -   Integration with API management tools: in the same way the logic of Wilma is available in API Umbrella, the
     implementation in other tools such us KONG and/or Proxy42 will be studied.