You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2019/07/12 01:19:18 UTC

[GitHub] [incubator-shardingsphere] yishenghuang opened a new issue #2695: data not decrypted in sharding-tables scenario

yishenghuang opened a new issue #2695: data not decrypted in sharding-tables scenario
URL: https://github.com/apache/incubator-shardingsphere/issues/2695
 
 
   ## Bug Report
   
   **For English only**, other languages will not accept.
   
   Before report a bug, make sure you have:
   
   - Searched open and closed [GitHub issues](https://github.com/apache/incubator-shardingsphere-example/issues).
   - Read documentation: [ShardingSphere Doc](https://shardingsphere.apache.org/document/current/en/overview).
   
   Please pay attention on issues you submitted, because we maybe need more details. 
   If no response **more than 7 days** and we cannot reproduce it on current information, we will **close it**.
   
   Please answer these questions before submitting your issue. Thanks!
   
   ### Which version of ShardingSphere did you use?
   4.0.0-RC1
   ### Which project did you use? Sharding-JDBC or Sharding-Proxy?
   Sharding-JDBC
   ### Expected behavior
   data should be decrypted when <sharding:encrypt-rules> correctly configured (sharding-tables scenario)
   ### Actual behavior
   1. data decrypted when selecting all records 
   2. data not decrypted when selecting records with sharding-key specified
   
   ### Reason analyze (If you can)
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
   configuratoin:
               <sharding:encrypt-rules>
   				<sharding:encryptor-rule id="card_encryptor" qualified-columns="card_info.card_pwd" type="AES" props-ref="props" />
   			</sharding:encrypt-rules>
   
   1. data decrypted
   [ShardingSphere-SQL] - Logic SQL: SELECT 	 
   		a.batch_no AS "batchNo",
   		a.type_id AS "cardType.id",
   		a.card_no AS "cardNo",
   		a.card_pwd AS "cardPwd",		
   		b.name as "cardType.name",
   		FROM card_info a
   		left join card_type b on a.type_id = b.id
   		 WHERE  a.batch_no = ? limit 30
   
   2. data not decrypted
   [ShardingSphere-SQL] - Logic SQL: SELECT 	 
   		a.batch_no AS "batchNo",
   		a.type_id AS "cardType.id",
   		a.card_no AS "cardNo",
   		a.card_pwd AS "cardPwd",		
   		b.name as "cardType.name",
   		FROM card_info a
   		left join card_type b on a.type_id = b.id limit 30
   
   ### Example codes for reproduce this issue (such as a github link).
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services