Hi, anyone have the solution about using CAS to integrate with OTRS system . thans and happy new year 2016!
[说明: 说明: 说明: 说明: Description: yx80] 广州越秀集团有限公司 Guangzhou Yuexiu Holding Limited 温鹤鸣 Winson Wen 信息中心 Information Center 广州市天河区珠江新城珠江西路5号广州国际金融中心65楼 65/Fl, Guangzhou International Finance Center, No.5 ZhuJiang Xi Rd, ZhuJiang New Town, GuangZhou, China Tel: +86 20 88836888 ext. 60114 | Fax: +86 20 88836668 Mobile: 13728013779 Http://www.yuexiu.com<http://www.yuexiu.com/> 发件人: [email protected] [mailto:[email protected]] 代表 Tom Andersson 发送时间: 2015年12月30日 18:05 收件人: CAS Community 主题: Re: [cas-user] WebFlow execution decryption problem OK nevermind, it was all about missing URL encoding, aka. user error, as suspected. Thanks though, Tom On Wednesday, 30 December 2015 11:48:29 UTC+2, Tom Andersson wrote: Sorry, reply slipped. So it seems to be decoded twice in some way? %2B -> + and then + -> whitespace. But this seems to happen quite early in the request processing, much before it's handled by spring or cas. What am I doing wrong or is it all just very broken? :) Thank you! Tom On Wednesday, 30 December 2015 11:45:17 UTC+2, Tom Andersson wrote: Hi, Thanks for the tips! It does indeed seem like a URL encoding or rather decoding issue. The base64 data seems to have been url-encoded fine, the + characters are encoded to %2B. However when the key reaches ClientFlowExecutionRepository, It has been decoded so that the + characters have been replaced by whitespace. It seems to be this way already after it's through On Tuesday, 29 December 2015 23:57:33 UTC+2, marvin.addison wrote: It seems like for some reason the execution key can not be decrypted. It then tries to redirect me to an error page but it seems to start looping as it still decrypt the execution. Quick sanity check looks ok. The base64 data following the underscore in the flow execution ID is the encoded ciphertext; taking the length of that data and multiplying by 3 and dividing by 4 gives a whole number, which is correct. Obviously such a simple check isn't very reassuring, but it is a sanity check that rules out obvious truncation of the execution ID. I'm pretty much out of ideas where to look next. Any pointers? I'd rule out URL encoding errors before looking into decoding and decryption minutia. M -- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/. -- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/.
