[jira] [Commented] (OPENMEETINGS-1864) new privacy regulations on the 25th May 2018

2018-04-11 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/OPENMEETINGS-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16434778#comment-16434778
 ] 

ASF subversion and git services commented on OPENMEETINGS-1864:
---

Commit e6ed0e19efb4671354250fb58c9a90aea1ff6b48 in openmeetings's branch 
refs/heads/OPENMEETINGS-1864-privacy from [~solomax]
[ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=e6ed0e1 ]

[OPENMEETINGS-1864] basic work on display deleted users


> new privacy regulations on the 25th May 2018
> 
>
> Key: OPENMEETINGS-1864
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1864
> Project: Openmeetings
>  Issue Type: Task
>Affects Versions: 4.0.2
>Reporter: Peter Dähn
>Assignee: Maxim Solodovnik
>Priority: Blocker
> Fix For: 4.0.4
>
>
> details in list
> [http://mail-archives.apache.org/mod_mbox/openmeetings-user/201804.mbox/%3Cbd7290bb-20d6-203a-22a9-25c0a1296da7%40vcrp.de%3E]
> Plan B:
> In Admin->User area
>  # display all users (deleted should be "read-only" with restore and purge 
> options only)
>  # add additional "Purge" button
>  # In case Purge will be selected:
>  ## User will be marked deleted
>  ## AsteriskSipUser and Address will be replaced with empty objects
>  ## User fields "age, externaluserid, firstname, lastname, login, pictureuri" 
> will be replaced with "Purged_some_hash"
>  ## User profile picture will be deleted
>  ## ChatMessage: fromName will be replaced with "Purged User" 
>  ## MailMessage: should be purged (some search by email will be required)
>  # UserIp need to be auto-masked after some configurable period of time in 
> all objects
>  # -History size in logs should be reduced to 7 days-
>  # There need to be a place to place a (customized) privacy policy.
>  # Registration-Dialog need to have a button/step to agree the data 
> processing. And to this belongs a button to disagree.
>  
> OK what need to be done for hard delete:
>  # delete user
>  # delete all user contacts (also users, so we might have recursion here)
>  # delete user from all groups
>  # delete user from room moderators
>  # delete all appointments with {{owner == user}}
>  # delete all calendars with {{owner == user}}
>  # delete all meeting members in appointments where {{owner != user}}
>  # delete all Private Messages where {{user}} is in to/from fields
>  # delete all UserContact + Requests
>  # delete all invitation sent by this user
>  # delete all private rooms owned by this user
>  # delete all user private files/recordings
>  # delete all chat messages send/received by this user
>  # clean email messages
>  # clean all Polls/answers



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[openmeetings] branch OPENMEETINGS-1864-privacy updated: [OPENMEETINGS-1864] basic work on display deleted users

2018-04-11 Thread solomax 
This is an automated email from the ASF dual-hosted git repository.

solomax pushed a commit to branch OPENMEETINGS-1864-privacy
in repository https://gitbox.apache.org/repos/asf/openmeetings.git


The following commit(s) were added to refs/heads/OPENMEETINGS-1864-privacy by 
this push:
 new e6ed0e1  [OPENMEETINGS-1864] basic work on display deleted users
e6ed0e1 is described below

commit e6ed0e19efb4671354250fb58c9a90aea1ff6b48
Author: Maxim Solodovnik 
AuthorDate: Thu Apr 12 07:54:19 2018 +0700

[OPENMEETINGS-1864] basic work on display deleted users
---
 .../db/dao/IGroupAdminDataProviderDao.java | 27 --
 .../apache/openmeetings/db/dao/room/RoomDao.java   |  4 ++--
 .../apache/openmeetings/db/dao/user/GroupDao.java  |  4 ++--
 .../apache/openmeetings/db/dao/user/UserDao.java   |  4 ++--
 .../openmeetings/web/admin/rooms/RoomForm.java |  2 +-
 .../openmeetings/web/common/GeneralUserForm.java   |  2 +-
 .../web/data/SearchableGroupAdminDataProvider.java |  4 ++--
 7 files changed, 35 insertions(+), 12 deletions(-)

diff --git 
a/openmeetings-db/src/main/java/org/apache/openmeetings/db/dao/IGroupAdminDataProviderDao.java
 
b/openmeetings-db/src/main/java/org/apache/openmeetings/db/dao/IGroupAdminDataProviderDao.java
index 6946af4..504fc7e 100644
--- 
a/openmeetings-db/src/main/java/org/apache/openmeetings/db/dao/IGroupAdminDataProviderDao.java
+++ 
b/openmeetings-db/src/main/java/org/apache/openmeetings/db/dao/IGroupAdminDataProviderDao.java
@@ -33,7 +33,20 @@ public interface IGroupAdminDataProviderDao exten
 * @param order - column and sort order
 * @return list of instances in the range specified
 */
-   List get(String search, Long adminId, int start, int count, String 
order);
+   List adminGet(String search, Long adminId, int start, int count, 
String order);
+
+   /**
+* Get a list of instances of {@link T}
+*
+* @param search - string search criteria to filter entities
+* @param start - the start to range to retrieve
+* @param count - maximum instance count to retrieve
+* @param order - column and sort order
+* @return list of instances in the range specified
+*/
+   default List adminGet(String search, int start, int count, String 
order) {
+   return get(search, start, count, order);
+   }
 
/**
 * Count the number of instances of {@link T}
@@ -42,5 +55,15 @@ public interface IGroupAdminDataProviderDao exten
 * @param adminId - id of group admin user
 * @return count of instances satisfying given search criteria
 */
-   long count(String search, Long adminId);
+   long adminCount(String search, Long adminId);
+
+   /**
+* Count the number of instances of {@link T}
+*
+* @param search - string search criteria to filter entities
+* @return count of instances satisfying given search criteria
+*/
+   default long adminCount(String search) {
+   return count(search);
+   }
 }
diff --git 
a/openmeetings-db/src/main/java/org/apache/openmeetings/db/dao/room/RoomDao.java
 
b/openmeetings-db/src/main/java/org/apache/openmeetings/db/dao/room/RoomDao.java
index f98e5ec..743b4cd 100644
--- 
a/openmeetings-db/src/main/java/org/apache/openmeetings/db/dao/room/RoomDao.java
+++ 
b/openmeetings-db/src/main/java/org/apache/openmeetings/db/dao/room/RoomDao.java
@@ -137,7 +137,7 @@ public class RoomDao implements 
IGroupAdminDataProviderDao {
}
 
@Override
-   public List get(String search, Long adminId, int start, int 
count, String order) {
+   public List adminGet(String search, Long adminId, int start, int 
count, String order) {
TypedQuery q = 
em.createQuery(DaoHelper.getSearchQuery("RoomGroup rg, IN(rg.room)", "r", null, 
search, true, true, false
, "rg.group.id IN (SELECT gu1.group.id FROM 
GroupUser gu1 WHERE gu1.moderator = true AND gu1.user.id = :adminId)", order, 
searchFields), Room.class);
q.setParameter("adminId", adminId);
@@ -159,7 +159,7 @@ public class RoomDao implements 
IGroupAdminDataProviderDao {
}
 
@Override
-   public long count(String search, Long adminId) {
+   public long adminCount(String search, Long adminId) {
TypedQuery q = 
em.createQuery(DaoHelper.getSearchQuery("RoomGroup rg, IN(rg.room)", "r", null, 
search, true, true, true
, "rg.group.id IN (SELECT gu1.group.id FROM 
GroupUser gu1 WHERE gu1.moderator = true AND gu1.user.id = :adminId)", null, 
searchFields), Long.class);
q.setParameter("adminId", adminId);
diff --git 
a/openmeetings-db/src/main/java/org/apache/openmeetings/db/dao/user/GroupDao.java
 
b/openmeetings-db/src/main/java/org/apache/openmeetings/db/dao/user/GroupDao.java
index c4f2a43..c44966f 100644
--- 
a/openmeetings-db/src/m

[jira] [Commented] (OPENMEETINGS-1866) Entity enums should be annotated with different namespaces

2018-04-11 Thread Maxim Solodovnik (JIRA) 

[ 
https://issues.apache.org/jira/browse/OPENMEETINGS-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433973#comment-16433973
 ] 

Maxim Solodovnik commented on OPENMEETINGS-1866:


I believe you have to enable "Namespace aware" (might be turned off by default)
As you can see the namespaces are different

> Entity enums should be annotated with different namespaces
> --
>
> Key: OPENMEETINGS-1866
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1866
> Project: Openmeetings
>  Issue Type: Task
>  Components: SOAP/REST API
>Affects Versions: 4.0.2
>Reporter: Maxim Solodovnik
>Assignee: Maxim Solodovnik
>Priority: Trivial
> Fix For: 4.0.3
>
>
> Entity enums should be annotated with different namespaces



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OPENMEETINGS-1866) Entity enums should be annotated with different namespaces

2018-04-11 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/OPENMEETINGS-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433943#comment-16433943
 ] 

Peter Dähn commented on OPENMEETINGS-1866:
--

sorry for the late response, but sill not able to compile it, because it 
complains about twice used 

http://www.w3.org/2001/XMLSchema"; 
targetNamespace="org.apache.openmeetings.user.type" version="1.0">

  
    
  
  
  
  
  
    
  


http://www.w3.org/2001/XMLSchema"; 
targetNamespace="org.apache.openmeetings.room.type" version="1.0">

  
    
  
  
  
    
  



 

Error during build:

 

[ERROR] Eine Klasse/Schnittstelle mit demselben Namen 
"org.apache.openmeetings.webservice.CalendarWebService.Type" wird bereits 
verwendet. Verwenden Sie eine Klassenanpassung, um diesen Konflikt zu lösen.
  Zeile 32 von http://server:5080/openmeetings/services/CalendarService?wsdl

[ERROR] eine weitere "Type" wird von hier generiert.
  Zeile 5 von http://server:5080/openmeetings/services/CalendarService?wsdl

Exception in thread "main" java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.codehaus.mojo.jaxws.Invoker.main(Invoker.java:78)
Caused by: com.sun.tools.ws.wscompile.AbortException
    at 
com.sun.tools.ws.processor.modeler.wsdl.JAXBModelBuilder.bind(JAXBModelBuilder.java:144)
    at 
com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildJAXBModel(WSDLModeler.java:2298)
    at 
com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.internalBuildModel(WSDLModeler.java:198)
    at 
com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModeler.java:141)
    at 
com.sun.tools.ws.wscompile.WsimportTool.buildWsdlModel(WsimportTool.java:444)
    at com.sun.tools.ws.wscompile.WsimportTool.run(WsimportTool.java:205)
    at com.sun.tools.ws.wscompile.WsimportTool.run(WsimportTool.java:183)
    ... 5 more

> Entity enums should be annotated with different namespaces
> --
>
> Key: OPENMEETINGS-1866
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1866
> Project: Openmeetings
>  Issue Type: Task
>  Components: SOAP/REST API
>Affects Versions: 4.0.2
>Reporter: Maxim Solodovnik
>Assignee: Maxim Solodovnik
>Priority: Trivial
> Fix For: 4.0.3
>
>
> Entity enums should be annotated with different namespaces



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OPENMEETINGS-1864) new privacy regulations on the 25th May 2018

2018-04-11 Thread Maxim Solodovnik (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OPENMEETINGS-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Solodovnik updated OPENMEETINGS-1864:
---
Description: 
details in list

[http://mail-archives.apache.org/mod_mbox/openmeetings-user/201804.mbox/%3Cbd7290bb-20d6-203a-22a9-25c0a1296da7%40vcrp.de%3E]

Plan B:
In Admin->User area
 # display all users (deleted should be "read-only" with restore and purge 
options only)
 # add additional "Purge" button
 # In case Purge will be selected:
 ## User will be marked deleted
 ## AsteriskSipUser and Address will be replaced with empty objects
 ## User fields "age, externaluserid, firstname, lastname, login, pictureuri" 
will be replaced with "Purged_some_hash"
 ## User profile picture will be deleted
 ## ChatMessage: fromName will be replaced with "Purged User" 
 ## MailMessage: should be purged (some search by email will be required)
 # UserIp need to be auto-masked after some configurable period of time in all 
objects
 # -History size in logs should be reduced to 7 days-
 # There need to be a place to place a (customized) privacy policy.
 # Registration-Dialog need to have a button/step to agree the data processing. 
And to this belongs a button to disagree.
 

OK what need to be done for hard delete:
 # delete user
 # delete all user contacts (also users, so we might have recursion here)
 # delete user from all groups
 # delete user from room moderators
 # delete all appointments with {{owner == user}}
 # delete all calendars with {{owner == user}}
 # delete all meeting members in appointments where {{owner != user}}
 # delete all Private Messages where {{user}} is in to/from fields
 # delete all UserContact + Requests
 # delete all invitation sent by this user
 # delete all private rooms owned by this user
 # delete all user private files/recordings
 # delete all chat messages send/received by this user
 # clean email messages
 # clean all Polls/answers

  was:
details in list

[http://mail-archives.apache.org/mod_mbox/openmeetings-user/201804.mbox/%3Cbd7290bb-20d6-203a-22a9-25c0a1296da7%40vcrp.de%3E]

Plan B:
In Admin->User area
 # display all users (deleted should be "read-only" with restore and purge 
options only)
 # add additional "Purge" button
 # In case Purge will be selected:
 ## User will be marked deleted
 ## AsteriskSipUser and Address will be replaced with empty objects
 ## User fields "age, externaluserid, firstname, lastname, login, pictureuri" 
will be replaced with "Purged_some_hash"
 ## User profile picture will be deleted
 ## ChatMessage: fromName will be replaced with "Purged User" 
 ## MailMessage: should be purged (some search by email will be required)
 # UserIp need to be auto-masked after some configurable period of time in all 
objects
 # History size in logs should be reduced to 7 days 
 

OK what need to be done for hard delete:
 # delete user
 # delete all user contacts (also users, so we might have recursion here)
 # delete user from all groups
 # delete user from room moderators
 # delete all appointments with {{owner == user}}
 # delete all calendars with {{owner == user}}
 # delete all meeting members in appointments where {{owner != user}}
 # delete all Private Messages where {{user}} is in to/from fields
 # delete all UserContact + Requests
 # delete all invitation sent by this user
 # delete all private rooms owned by this user
 # delete all user private files/recordings
 # delete all chat messages send/received by this user
 # clean email messages
 # clean all Polls/answers


> new privacy regulations on the 25th May 2018
> 
>
> Key: OPENMEETINGS-1864
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1864
> Project: Openmeetings
>  Issue Type: Task
>Affects Versions: 4.0.2
>Reporter: Peter Dähn
>Assignee: Maxim Solodovnik
>Priority: Blocker
> Fix For: 4.0.4
>
>
> details in list
> [http://mail-archives.apache.org/mod_mbox/openmeetings-user/201804.mbox/%3Cbd7290bb-20d6-203a-22a9-25c0a1296da7%40vcrp.de%3E]
> Plan B:
> In Admin->User area
>  # display all users (deleted should be "read-only" with restore and purge 
> options only)
>  # add additional "Purge" button
>  # In case Purge will be selected:
>  ## User will be marked deleted
>  ## AsteriskSipUser and Address will be replaced with empty objects
>  ## User fields "age, externaluserid, firstname, lastname, login, pictureuri" 
> will be replaced with "Purged_some_hash"
>  ## User profile picture will be deleted
>  ## ChatMessage: fromName will be replaced with "Purged User" 
>  ## MailMessage: should be purged (some search by email will be required)
>  # UserIp need to be auto-masked after some configurable period of time in 
> all objects
>  # -History size in logs should be reduced to 7 days-
>  # There need to be a place to place a (cus

[jira] [Created] (OPENMEETINGS-1867) isEnabled/isVisible/Wizard need to be improved

2018-04-11 Thread Maxim Solodovnik (JIRA) 
Maxim Solodovnik created OPENMEETINGS-1867:
--

 Summary: isEnabled/isVisible/Wizard need to be improved
 Key: OPENMEETINGS-1867
 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1867
 Project: Openmeetings
  Issue Type: Improvement
  Components: HTML5
Affects Versions: 5.0.0
Reporter: Maxim Solodovnik
Assignee: Maxim Solodovnik
 Fix For: 5.0.0


isEnabled/isVisible/Wizard need to be improved as described in

https://issues.apache.org/jira/browse/WICKET-6541



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OPENMEETINGS-1864) new privacy regulations on the 25th May 2018

2018-04-11 Thread Maxim Solodovnik (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OPENMEETINGS-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Solodovnik updated OPENMEETINGS-1864:
---
Description: 
details in list

[http://mail-archives.apache.org/mod_mbox/openmeetings-user/201804.mbox/%3Cbd7290bb-20d6-203a-22a9-25c0a1296da7%40vcrp.de%3E]

Plan B:
In Admin->User area
 # display all users (deleted should be "read-only" with restore and purge 
options only)
 # add additional "Purge" button
 # In case Purge will be selected:
 ## User will be marked deleted
 ## AsteriskSipUser and Address will be replaced with empty objects
 ## User fields "age, externaluserid, firstname, lastname, login, pictureuri" 
will be replaced with "Purged_some_hash"
 ## User profile picture will be deleted
 ## ChatMessage: fromName will be replaced with "Purged User" 
 ## MailMessage: should be purged (some search by email will be required)
 # UserIp need to be auto-masked after some configurable period of time in all 
objects
 # History size in logs should be reduced to 7 days 
 

OK what need to be done for hard delete:
 # delete user
 # delete all user contacts (also users, so we might have recursion here)
 # delete user from all groups
 # delete user from room moderators
 # delete all appointments with {{owner == user}}
 # delete all calendars with {{owner == user}}
 # delete all meeting members in appointments where {{owner != user}}
 # delete all Private Messages where {{user}} is in to/from fields
 # delete all UserContact + Requests
 # delete all invitation sent by this user
 # delete all private rooms owned by this user
 # delete all user private files/recordings
 # delete all chat messages send/received by this user
 # clean email messages
 # clean all Polls/answers

  was:
details in list

[http://mail-archives.apache.org/mod_mbox/openmeetings-user/201804.mbox/%3Cbd7290bb-20d6-203a-22a9-25c0a1296da7%40vcrp.de%3E]


OK what need to be done for hard delete:
 # delete user
 # delete all user contacts (also users, so we might have recursion here)
 # delete user from all groups
 # delete user from room moderators
 # delete all appointments with {{owner == user}}
 # delete all calendars with {{owner == user}}
 # delete all meeting members in appointments where {{owner != user}}
 # delete all Private Messages where {{user}} is in to/from fields
 # delete all UserContact + Requests
 # delete all invitation sent by this user
 # delete all private rooms owned by this user
 # delete all user private files/recordings
 # delete all chat messages send/received by this user
 # clean email messages
 # clean all Polls/answers 




> new privacy regulations on the 25th May 2018
> 
>
> Key: OPENMEETINGS-1864
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1864
> Project: Openmeetings
>  Issue Type: Task
>Affects Versions: 4.0.2
>Reporter: Peter Dähn
>Assignee: Maxim Solodovnik
>Priority: Blocker
> Fix For: 4.0.4
>
>
> details in list
> [http://mail-archives.apache.org/mod_mbox/openmeetings-user/201804.mbox/%3Cbd7290bb-20d6-203a-22a9-25c0a1296da7%40vcrp.de%3E]
> Plan B:
> In Admin->User area
>  # display all users (deleted should be "read-only" with restore and purge 
> options only)
>  # add additional "Purge" button
>  # In case Purge will be selected:
>  ## User will be marked deleted
>  ## AsteriskSipUser and Address will be replaced with empty objects
>  ## User fields "age, externaluserid, firstname, lastname, login, pictureuri" 
> will be replaced with "Purged_some_hash"
>  ## User profile picture will be deleted
>  ## ChatMessage: fromName will be replaced with "Purged User" 
>  ## MailMessage: should be purged (some search by email will be required)
>  # UserIp need to be auto-masked after some configurable period of time in 
> all objects
>  # History size in logs should be reduced to 7 days 
>  
> OK what need to be done for hard delete:
>  # delete user
>  # delete all user contacts (also users, so we might have recursion here)
>  # delete user from all groups
>  # delete user from room moderators
>  # delete all appointments with {{owner == user}}
>  # delete all calendars with {{owner == user}}
>  # delete all meeting members in appointments where {{owner != user}}
>  # delete all Private Messages where {{user}} is in to/from fields
>  # delete all UserContact + Requests
>  # delete all invitation sent by this user
>  # delete all private rooms owned by this user
>  # delete all user private files/recordings
>  # delete all chat messages send/received by this user
>  # clean email messages
>  # clean all Polls/answers



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)