kingmouse-yx commented on issue #6564:
URL: https://github.com/apache/apisix/issues/6564#issuecomment-1064289505


   @soulbird 
   Hello, finally I found the location of this issue: lrucache
   ```lua
   local consumers = lrucache("consumers_key", consumer_conf.conf_version,
           create_consume_cache, consumer_conf)
   
       local consumer = consumers[user_key]
   
       -- The following two lines of code were added by me.
       core.log.warn("user_key ",user_key)
       core.log.warn("consumer: ",core.json.encode(consumer,true))
   ```
   In the log, I found the value of user-key is fixed, but the value of 
consumer is different(`secret value`). The log is as follows:
   ```log
   2022/03/10 16:40:17 [warn] 43#43: *1465247 [lua] jwt-auth.lua:295: 
phase_func(): consumer: 
{"auth_conf":{"base64_secret":false,"key":"test01","algorithm":"HS256","exp":86400,"secret":"VIN\/yaVQeSk5VcQ\/Tln9OMKViC7xUNWgxQue6UM4NcQ=","disable":false},"create_time":1646723289,"update_time":1646929454,"id":"test01","username":"test01","consumer_name":"test01","plugins":{"jwt-auth":"table:
 0x4afa5e83de10"}}, client: 172.18.0.1, server: _, request: "POST /get04 
HTTP/1.1", host: "127.0.0.1:9080"
   2022/03/10 16:40:17 [warn] 42#42: *1465245 [lua] jwt-auth.lua:295: 
phase_func(): consumer: 
{"auth_conf":{"base64_secret":false,"key":"test01","algorithm":"HS256","exp":86400,"secret":"YStztFps1YK+XmnoPJepSSySkQ5mMljZ9OSex3gMAdk=","disable":false},"create_time":1646723289,"update_time":1646929454,"id":"test01","username":"test01","consumer_name":"test01","plugins":{"jwt-auth":"table:
 0x4afa5e47ab48"}}, client: 172.18.0.1, server: _, request: "POST /get04 
HTTP/1.1", host: "127.0.0.1:9080"
   ```
   > Note: in this test, I set base64_secret'value to false


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to