hi，@dosu Thank you for your receipt。Is it necessary to configure the openid-connect plugin? Because the only way I get the dynamic token is through a basic auth authentication http interface. After successfully calling the http interface with the username and password, a json containing a token attribute is returned. Then I need to set this token to the header of the route rewrite. Thank you!

You don't need to configure the openid-connect plugin if you are obtaining the token through a basic auth authentication HTTP interface. You can achieve this using the serverless-pre-function plugin to make an HTTP request to obtain the token and set it in the request header.

Here is how you can do it:

1. Create a Plugin Config:

   curl "http://127.0.0.1:9180/apisix/admin/plugin_configs/1" -X PUT -d '
   {
       "plugins": {
           "serverless-pre-function": {
               "phase": "rewrite",
               "functions" : ["return function(conf, ctx)
                   -- Import necessary libraries
                   local core = require(\"apisix.core\")
                   local http = require(\"resty.http\")
   
                   -- Make an HTTP request to obtain the token
                   local httpc = http.new()
                   local res, err = httpc:request_uri(\"https://your-auth-server.com/token\", {
                       method = \"POST\",
                       body = \"grant_type=client_credentials&client_id=your_client_id&client_secret=your_client_secret\",
                       headers = {
                           [\"Content-Type\"] = \"application/x-www-form-urlencoded\",
                           [\"Authorization\"] = \"Basic \" .. ngx.encode_base64(\"username:password\")
                       },
                       ssl_verify = false
                   })
   
                   if not res then
                       core.log.error(\"failed to request token: \", err)
                       return
                   end
   
                   local token = core.json.decode(res.body).access_token
   
                   if token then
                       -- Set the token in the request header
                       core.request.set_header(ctx, \"Authorization\", \"Bearer \" .. token)
                   else
                       core.log.error(\"failed to obtain access token\")
                   end
               end"]
           }
       }
   }'

2. Configure a new Route:

   curl "http://127.0.0.1:9180/apisix/admin/routes/1" -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
   {
       "name": "Your Route Name",
       "desc": "Description of your route",
       "methods": ["GET", "POST"],  # Adjust methods as needed
       "uri": "/your/route/uri",
       "upstream": {
           "nodes": {
               "your-upstream-service:port": 1
           },
           "type": "roundrobin"
       },
       "plugin_config_id": 1
   }'

In this setup:

• The serverless-pre-function plugin makes an HTTP request to your authentication server using basic auth to obtain the token.
• The token is then set in the Authorization header of the request before it is forwarded to the upstream service.

Replace https://your-auth-server.com/token, your_client_id, your_client_secret, username, password, and other placeholders with your actual values.

This approach allows you to dynamically obtain a token and set it in the request header without needing the openid-connect plugin ^[1][2].

To continue talking to Dosu, mention @dosu.

Thank you again for your help. I use basic-auth for the routing authentication plug-in, and an error {"message":"Invalid authorization in request"} will appear. But changing "phase": "rewrite" in the serverless-pre-function plug-in to "phase": "before_proxy" makes it work properly. Thank you!

@Dusu Can the return function in functions be defined independently in the plugin file?

Yes, the return function in the functions can be defined independently in the plugin file. The provided code snippets show that the functions are defined as strings within the plugin configurations. For example:

"functions" : ["return function(conf, ctx)
                ngx.say(\"serverless-post-function\");
                end"]

This indicates that the return function is defined within the plugin configuration itself, and not separately in the plugin file. According to the documentation, only Lua functions are allowed, and they can be anonymous functions or closures. Other Lua code is not permitted ^[1][2].

To continue talking to Dosu, mention @dosu.