An introduction to the new experimental authorization server implementation - version 0.0.1 

Thanks. Yes. Maybe later I'll also make some videos on reactive spring as well :)

@@laurspilca Great!, Thank you...

Hey. No. You should follow the playlist. At some point, I'll make a separate playlist about the new authorization server. In these videos, I presented the first version while they appeared. But mind that they were not even mentioned as being community supported yet. So things changed meanwhile.

Thanks, Azeem. Good question. I'm not sure if it will be integrated with Spring Cloud. I didn't hear anything on this yet.

Hi. I do recommend you use the version 1.x. It is out now already and you find examples for using it in my Spring Security 2022 playlist.

@@laurspilca Yes I've started with that but after haveing a lot of confusion in your video 11 due to mentioning things which you explained in a different playlist. But anyways thank you!

Hello. Good question. Not sure if you can customize this. But what is the use case for that?

@@laurspilca With the standard grant type, I don't need to care about that. For example, with authorization code grant type, after the user authentication code is returned, the client will use the code and client credential(client id, client secret) in the next request to get token as I observed in the video. However, in case I want to customize my own grant type, I don't know whether to authenticate the client or the user first, but I think client authentication first is more reasonable. I want to get more opinions from you?

Hi. Password grant type is deprecated. Normally it's best you use authorization code instead.