instantiator | library provides a way of avoiding usage

1. In the procedure’s signature the formal parameter reference does not indicate a data type, but is declared as a variable parameter.
2. Typeless parameters are not legal in Pascal, but permitted in dialects such as GNU Pascal and FreePascal. There, such variable parameters accept actual parameters of any data type. The compiler will not enforce/restrict permissible data types, but it must be addressable (i. e. literals are not permitted).
3. dataTypeName(expression) is indeed a typecast (also illegal in Pascal, but allowed by some dialects). Specifically, dataTypeName(variableName) is a variable typecast. It will be treated as if variableName was of the named data type. This is necessary, because in this particular case reference has no associated data type. No associated data type means, there is no agreed rule in how to access the variable in question (i. e. any read/write access is impossible).
4. The procedure probably creates an instance of TComponentClass, i. e. the data type of the parameter InstanceClass, but there you should really read the documentation of the NewInstance method. I can only tell you it’s a descendant of TComponent otherwise it hardly makes sense to typecast to an unrelated class.

So I'd recommend against using a random library on github that hasn't been updated in 4 years. In fact I'd recommend against using a random library on github at all unless you've read every line of code and done a security audit (as well as one on any weird library it drags in). But if you're going to do this, I'd suggest you just take the source code of their library and drop it into your project, rather than try to use it as a library. It's not like you'll be missing out on updates, and it will be easier than fixing a 4 year old gradle system.

Try switching the column in database for location from type of point to type geometry

Also use all the following properties

The id in portal_user_user_type should be autogenerated but is id bigint NOT NULL?

But portal_user_user_type only holds a reference to the User and the UserType. So you could easily simplify your model.

Something like:

Using --data-urlencode curl option, you are adding a parameter to the request's body. In your Kotlin code, you are not passing the same data in the request's body, but in the headers.

What you should do (to mimic postman behavior) is to pass grant_type, client_id, client_secret in the request body by using BodyInserters, like this:

You need to instantiate a class instance here. do this:

I fixed by adding MockitoAnnotations.initMocks(this) to setup method

Take a look at the top of stack trace closely, and you'll see that Log4j is complaining about this element:

One potential problem could be with your Java package structure. Spring Boot does by default only look for annotated within the Java package (and it's children) that contains the Application class.

If your OktaService is in a location of your package structure, then it won't be found by default. As an example, if you have Application in com.example.myapp.ui and OktaService in com.example.myapp.service, then it won't work. If this is the case, then you can either change your package structure or set the scanBasePackages property in @SpringBootApplication to define a location that covers the entire application.