Iris: [BUG/Feature] MVC Dependency authentication example

[Dexus]

Describe the bug
on the master branch "https://github.com/kataras/iris/blob/master/_examples/mvc/authenticated-controller/main.go" an authentication is used to show how it is done when you search for an authenticated user.
But how can I find an unauthenticated user who can call the same route but from a different controller?

To Reproduce
Steps to reproduce the behavior:

1. [...]

Expected behavior
Let's take two controllers that are both registered for the same route, but one of them has no authentication feature. Now when I call the route, I want the call without authentication to return a different value than if I were authenticated.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. ubuntu, windows]

Additional context
I don't think it's a bug, but a feature request, although I think others do as well, that the same route should call a different controller under different circumstances.

[kataras]

Each Controller's method creates a new route, so two controllers can't share the same route with the current implementation. If I am going to change the MVC again, the v12.2.0 release will be delayed even more, I will think of it and come back to you with a solution.

[Dexus]

Thanks for the feedback. I look forward to your proposed solution.
It is sometimes bewitching that it is possible with basic functions, again in the MVC something difficult or not at all. But doing it this way will always make things a bit better.

[kataras]

Hello @Dexus, I did it without any changes (however you could do it by checking the Authenticated integer value (if == 0 then unauthenticated) on the UserController.GetMe). This feature is available across Iris application, not just MVC. You just Party.SetRegisterRule(iris.RouteOverlap). Updated user authenticated controller example. Please tell me if that suits your needs.

https://github.com/kataras/iris/blob/abd6ed4d40983ab13bdbce6dd74db7bfc38e7db8/_examples/mvc/authenticated-controller/main.go#L27-L32

https://github.com/kataras/iris/blob/abd6ed4d40983ab13bdbce6dd74db7bfc38e7db8/_examples/mvc/authenticated-controller/main.go#L54-L68

https://github.com/kataras/iris/blob/abd6ed4d40983ab13bdbce6dd74db7bfc38e7db8/_examples/mvc/authenticated-controller/main.go#L41-L42

https://github.com/kataras/iris/blob/abd6ed4d40983ab13bdbce6dd74db7bfc38e7db8/_examples/mvc/authenticated-controller/main.go#L73-L77

https://github.com/kataras/iris/blob/abd6ed4d40983ab13bdbce6dd74db7bfc38e7db8/_examples/mvc/authenticated-controller/main.go#L102-L108

[Dexus]

Hi @kataras,

thank you, it works perfectly, just as I imagined it would. That makes things a lot easier now.

[kataras]

I am glad it helped, do you think it would be easier to default this rule on mvc apps?

[Dexus]

That's a good question. I think it always depends on the use case.

If I just relate it to my work and the projects I've done in the past, it might fit quite well as a default.

Just for websites with frontend I would prefer it as default. For API Entpoints, it does not always make sense.

I think a warning with debug might be helpful there depending on the setting of the SetRegisterRule. So you know why a route was not registered, but that's just a thought that would help me, because I had the problem ;)

[kataras]

I think a warning with debug might be helpful there depending on the setting of the SetRegisterRule. So you know why a route was not registered, but that's just a thought that would help me, because I had the problem ;)

Yes, now this new route registration rule is described in the example too. The RouteError rule will force the app to stop with an error on duplicate routes, the RouteSkip will just silent skip duplicate, the RouteOverride (the default one) will replace the old one with the new one and RouteOverlap as described in the previous comment. ~So, you think it's better to add Warning messages on RouteSkip and RouteOverride?~ I think it's better to let it as it's, no need to depend on the logger on APIBuilder, we only return errors there. And for mvc apps we could make it default-ed, the new rule, but this may introduce hidden breaking change to existing applications, I think the updated example with this rule there it's the best possible thing for that type of things.

[Dexus]

I think that's good. It's so right for me.

[Dexus]

Hi @kataras

while i code for the certification, i found a crazy problem

[HTTP Server] http: panic serving 127.0.0.1:62225: reflect: Call using *controller.CustomerPrivateController as type *controller.CustomerController

Here a bit code:

// BaseController desc
type BaseController struct {
    Session       *sessions.Session
    CurrentUserID Authenticated
    Ctx           iris.Context
}

// CustomerController serves the "public" Customer API.
type CustomerController struct {
    Ctx iris.Context
}

// Get desc
// Route /category/ [GET]
func (cuc *CustomerController) Get() {
    cuc.Ctx.JSON(data)
    return
}


// CustomerPrivateController serves the "public-private" Customer API.
type CustomerPrivateController struct{ BaseController }

// Get desc
// Route /category/ [GET]
func (cupc *CustomerPrivateController) Get() *models.Category {
    return new(models.Category)
}

Do you know what is happening here?

[kataras]

Hello @Dexus,

Thanks for the report! It should be fixed, update to the master one.

[Dexus]

@kataras
Thank you, works now as expected.

[Dexus]

@kataras
One question, is there a way to register dependencies global, so it would not need to repeat all the registrations for each route?

[kataras]

@kataras
One question, is there a way to register dependencies global, so it would not need to repeat all the registrations for each route?

Hello @Dexus,

The mvc/Application.Register registers the dependencies for all routes and controllers on that mvc Application. Do you mean for all MVC application instances? If so, then, yes you can:

• Each iris.Party has its dependencies ( parent Party's are inherited). They are used to register route handlers with dependency injection (previously named as "hero handlers") with the Party.ConfigureContainer(... func(api *iris.APIContainer))

https://github.com/kataras/iris/tree/master/_examples/dependency-injection

• On mvc.New/Configure you get a new mvc Application instance for a target Party, as we already know. All dependencies from that target iris.Party are cloned and passed to that mvc Application.

• So, if you do:

app := iris.New()
app.ConfigureContainer(func(api *iris.APIContainer){
  api.RegisterDependency(%yourdep%)
  // [...]
})

m := mvc.New(app /* or any other iris.Party */)
m.Handle(new(myController))
// no need to m.Register the %yourdep%,
// it's inherited from the target party (the root app in this case)

// The %yourdep% dependency is registered to that mvc Application
// and its controllers automatically as well.
m2 := mvc.New(app.Party("/user"))
m2.Handle(new(userController))

// [...]

[Dexus]

Thanks for the reminder. I don't know why I forgot that again, use it in a project like this.

[kataras]

No worries @Dexus, you can also check the database/mysql new example for some kind of "help" as well.

Also, I have just pushed another new cool feature: versioned controllers, example at: https://github.com/kataras/iris/tree/master/_examples/mvc/versioned-controller

[Dexus]

Also, I have just pushed another new cool feature: versioned controllers, example at: https://github.com/kataras/iris/tree/master/_examples/mvc/versioned-controller

Thats a very cool feature!

[kataras]

Yes @Dexus!

I've added another example that may be helpful for you as well: https://github.com/kataras/iris/tree/master/_examples/mvc/overview

                                         +-------------------+
                                         |  Env (DEV, PROD)  |
                                         +---------+---------+
                                         |         |         |
                                         |         |         |
                                         |         |         |
                                    DEV  |         |         |  PROD
-------------------+---------------------+         |         +----------------------+-------------------
                   |                               |                                |
                   |                               |                                |
               +---+-----+        +----------------v------------------+        +----+----+
               | sqlite  |        |         NewDB(Env) DB             |        |  mysql  |
               +---+-----+        +----------------+---+--------------+        +----+----+
                   |                               |   |                            |
                   |                               |   |                            |
                   |                               |   |                            |
      +------------+-----+     +-------------------v---v-----------------+     +----+------+
      |  greeterWithLog  |     |  NewGreetService(Env, DB) GreetService  |     |  greeter  |
      -------------+-----+     +---------------------------+-------------+     +----+------+
                   |                                       |                        |
                   |                                       |                        |
                   |           +-----------------------------------------+          |
                   |           |  GreetController          |             |          |
                   |           |                           |             |          |
                   |           |  - Service GreetService <--             |          |
                   |           |                                         |          |
                   |           +-------------------+---------------------+          |
                   |                               |                                |
                   |                               |                                |
                   |                               |                                |
                   |                   +-----------+-----------+                    |
                   |                   |      HTTP Request     |                    |
                   |                   +-----------------------+                    |
                   |                   |  /greet?name=kataras  |                    |
                   |                   +-----------+-----------+                    |
                   |                               |                                |
+------------------+--------+         +------------+------------+           +-------+------------------+
|  model.Response (JSON)    |         |  Response (JSON, error) |           |  Bad Request             |
+---------------------------+         +-------------------------+           +--------------------------+
|  {                        |                                               |  mysql: not implemented  |
|    "msg": "Hello kataras" |                                               +--------------------------+
|  }                        |
+---------------------------+