Update credits, package.json and roadmap.md

CREDITS

@@ -8,11 +8,12 @@ Teresa Sempere <teresasempere>
 Ana Estrada Martos <aemartos>
 fiware-austria <fiware-austria>
 Kazuhito Suda <fisuda>
-kushagrasrivastva-NEC <kushagrasrivastva-NEC>
 Enrique Barra Arias <ebarra>
+kushagrasrivastva-NEC <kushagrasrivastva-NEC>
 Lourdes Marco <Lourdesmarco>
+Anthony Garcia <digigarlab>
+Stopkin Sergey <sstopkin>
 Sergio Romero Barra<sergiorb>
-codacy-badger <codacy-badger>
 Javi Carnero <emepetres>
 iaoiui <iaoiui>
 hspark sukeypark <sukeypark>

package.json

@@ -1,6 +1,6 @@
 {
   "name": "fiware-idm",
-  "version": "7.8.0",
+  "version": "7.8.1",
   "private": true,
   "license": "MIT",
   "scripts": {

roadmap.md

@@ -20,18 +20,15 @@ any time.
 The following list of features are planned to be addressed in the short term,
 and incorporated in the next release of the product planned for February 2019:
 
--   CORS Support: for being able to send HTTP requests from Web applications to
-    Keyrock's REST API.
+-   Extend Unit tests: to be run in CI
 
--   Internationalization: for supporting the configuration of different
-    languages in the UI:
-
--   Sign out endpoint: for signing out user's sessions from OAuth 2.0 clients.
+-   OpenID Connect: support to this standard as an extension of the current
+    OAuth 2.0 implementation.
 
--   Unit tests: to be run in CI
+-   2 factor authentication: support two levels of authentication based on
+    email/password + QR
 
--   PostgreSQL compatibility: for supporting this technology as an alternative
-    of MySQL.
+-   Enable users to manage access to their data by third party applications
 
 ## Medium term
 
@@ -42,11 +39,10 @@ next planned release:
 -   Improvements in AZF integration: general improvements for better supporting
     new Keyrock's features
 
--   OpenID Connect: support to this standard as an extension of the current
-    OAuth 2.0 implementation.
+-   COAP compatibility: supporting this protocol as an alternative of HTTP could
+    improve the performance of IoT devices authentication process.
 
--   UMA integration: support for improvements that UMA provides with respect to
-    the current OAuth 2.0 based authorization mechanism.
+-   Data Usage Control: extend existing functionalities.
 
 ## Long term
 
@@ -55,11 +51,5 @@ of the product even though development 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
 
--   Data Usage Control: compatibility with the new Data Usage Control paradigm
-    created together with the Context Management (Core) Chapter.
-
 -   Integration with Alastria identity, Hyperledger Indy: for supporting
     blockchain-based authentication mechanisms.
-
--   COAP compatibility: supporting this protocol as an alternative of HTTP could
-    improve the performance of IoT devices authentication process.