weasley-j / chinaport-data-signature Goto Github PK

China E-Port Data Signature, **电子口岸海关总署'CEBXxxMessage末三段进出口单报文'和'海关179号数据抓取报文'的加签应用。该应用支持JSON报文直推、加签失败时通过邮件进行通知、在电子口岸u-key健康状态异常导致加签失败时自动重启Windows Websocket客户端等功能。该项目具备开箱即用的特点，无需安装任何中间件，并且无需进行二次编译安装。

License: GNU General Public License v3.0

Java 62.49% JavaScript 20.19% Shell 0.29% Dockerfile 0.06% HTML 16.98%

java ceb customs sign-data china-e-port-data-signature ceb-message ceb311message ceb621message

chinaport-data-signature's People

Contributors

Stargazers

Watchers

Forkers

tangzp noany-cn hetuan ledccn juentech gogomarine xinerivg cfzhangwl bonyz zelentre newcardriver tomao2014 caribbean08 whjstc wuzm01211 wilsonleeee pengxianfeng jwillim 1783cwf mustangzhong llogin formating whaiq gongqf xianyucoder baoxina baoxin1 pdw563 leeonsoft sharp lebu9527 corner4world zjzm 31867 rainseason jovenking imlyk jumpalang heiletian itears-lt sunjob-max pypypk 15001167619 yanglei9999 cls1997

chinaport-data-signature's Issues

大佬你好,我是2023年的新key,推送311报文,查看回执返回签名错误

证书替换成了自己的证书,服务正常启动,返回正常.
下文是插入的签名参数:(貌似评论会吞掉<>这种格式错误,请忽略)
<ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
ds:SignedInfo
<ds:CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"></ds:CanonicalizationMethod>
<ds:SignatureMethod Algorithm="http://www.chinaport.gov.cn/2022/04/xmldsig#sm2-sm3"></ds:SignatureMethod>
<ds:Reference URI="">
ds:Transforms
<ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"></ds:Transform>
</ds:Transforms>
<ds:DigestMethod Algorithm="http://www.chinaport.gov.cn/2022/04/xmldsig#sm3"></ds:DigestMethod>
ds:DigestValue{data["digestValue"]}</ds:DigestValue>
</ds:Reference>
</ds:SignedInfo>
ds:SignatureValue
{data["signatureValue"]}
</ds:SignatureValue>
ds:KeyInfo
ds:KeyName{data["certNo"]}</ds:KeyName>
ds:X509Data
ds:X509Certificate
{data["x509Certificate"]}
</ds:X509Certificate>
</ds:X509Data>
</ds:KeyInfo>
</ds:Signature>

> ![image](https://user-images.githubusercontent.com/24217780/187187468-67fa94b5-cb74-49b5-b66b-41664193aca9.png)

报错信息

试试以下的方式：
1 检查下加签的数据格式，字符串是需要转义的
2 下载源码debug下，maven依赖在release里面下载

Originally posted by @Weasley-J in #5 (comment)

启动了日志乱码问题

依赖要更新了xxx-M3的依赖都下不下来了

往海关发送自己拼接的加签后报文，是否需要过一遍C14N再发

XML报文加签获取信息成功后，自己拼接了加签报文。自己提取了Signature后验签没通过。过了遍c14n后再提取Signature验签就通过了。那是否往海关发之前整体报文需要过一遍c14n？

在第一次提交代码之前，地球上的搜索引擎在那个时间点[2022-02-14]之前还找不到任何有参价值的信息......

？？？？？

网上早就有了类似的之前做过的

大佬，加签过程优盾灭了求助

大佬，想咨询个问题，我们这边您的这个服务部署在linux云服务器上，优盾在内网的windows电脑上面，总是会出现一种问题就是优盾在收到数据后灯闪着闪着就灭了再也不亮了，然后就加签失败，想问一下这会是哪里的问题，有没有解决办法。

大佬为啥单一窗口文档中需要开通MQ通信方式而源码中未提及

https://www.singlewindow.cn/#/documentDetail?cid=A01-sic-apply&ctype=1

Maven仓库有些依赖下载不下来

想问下作者，Maven仓库的地址用的那个？换了几个仓库依赖下载不下来没法运行

WebSocketWrapper Bean实例并发读写问题

chinaport-data-signature/src/main/java/cn/alphahub/eport/signature/core/SignHandler.java

Lines 110 to 123 in 7935962

    
           public SignResult sign(@Valid SignRequest request, @NotBlank(message = "websocket发送的数据载荷不能为空") String payload) { 
        
               log.info("收到u-key加签数据: {}", payload); 
        
               WebSocketWrapper wrapper = webSocketClientHandler.getWebSocketWrapper(); 
        
               wrapper.setPayload(payload); 
        
               wrapper.setRequest(request); 
        
               wrapper.setSignResult(new SignResult()); 
        
               wrapper.setThreadReference(new AtomicReference<>(Thread.currentThread())); 
        
               if (SignHandler.isSignXml(request)) { 
        
                   wrapper.getSignResult().setDigestValue(SignatureHandler.getDigestValueOfCEBXxxMessage(request.getData())); 
        
               } 
        
               WebSocketConnectionManager manager = new WebSocketConnectionManager(standardWebSocketClient, webSocketClientHandler, properties.getWsUrl()); 
        
               manager.start();

websocketClientHandler Bean实例的 webSocketWrapper属性值没有考虑并发场景下的访问控制

"sessionID":"ad2254-8hewyf32-55616249"||"payExchangeInfoHead":"{"guid":"9D55BA71-22DE-41F4-8B50-C36C83B3B530","initalRequest":"原始请求","initalResponse":"ok","ebpCode":"4404840022","payCode":"312226T001","payTransactionId":"2018121222001354081010726129","totalAmount":100,"currency":"142","verDept":"3","payType":"1","tradingTime":"20181212041803","note":"批量订单，测试订单优化,生成多个so订单"}"||"payExchangeInfoLists":"[{"orderNo":"SO1710301150602574003","goodsInfo":[{"gname":"lhy-gnsku3","itemLink":"http://m.yunjiweidian.com/yunjibuyer/static/vue-buyer/idc/index.html#/detail?itemId=999761&shopId=453"},{"gname":"lhy-gnsku2","itemLink":"http://m.yunjiweidian.com/yunjibuyer/static/vue-buyer/idc/index.html#/detail?itemId=999760&shopId=453"}],"recpAccount":"OSA571908863132601","recpCode":"","recpName":"YUNJIHONGKONGLIMITED"}]"||"serviceTime":"1544519952469"

请教一下：
诸如以上的字符串如何在postman的请求body里面表达

您好，想请教个问题

推送311报文之后一直反馈验签失败而且报错也是文档中不存在的状态码属实难以理解，这边我用到的也是sm3或是sha1计算摘要均失败了

	public SignResult sign(@Valid SignRequest request, @NotBlank(message = "websocket发送的数据载荷不能为空") String payload) {
	log.info("收到u-key加签数据: {}", payload);

	WebSocketWrapper wrapper = webSocketClientHandler.getWebSocketWrapper();
	wrapper.setPayload(payload);
	wrapper.setRequest(request);
	wrapper.setSignResult(new SignResult());
	wrapper.setThreadReference(new AtomicReference<>(Thread.currentThread()));
	if (SignHandler.isSignXml(request)) {
	wrapper.getSignResult().setDigestValue(SignatureHandler.getDigestValueOfCEBXxxMessage(request.getData()));
	}

	WebSocketConnectionManager manager = new WebSocketConnectionManager(standardWebSocketClient, webSocketClientHandler, properties.getWsUrl());
	manager.start();