On Mon, Jun 25, 2018 at 11:33 AM, Senthalan Kanagalingam wrote:
> Hi Sagara,
>
>
> On Mon, Jun 25, 2018 at 10:44 AM Sagara Gunathunga
> wrote:
>
>>
>>
>> How this new architecture works with application-authentication.xml
>> file, say we have same parameter name with different names in
>>
Hi Sagara,
On Mon, Jun 25, 2018 at 10:44 AM Sagara Gunathunga wrote:
>
>
> How this new architecture works with application-authentication.xml file,
> say we have same parameter name with different names in
> application-authentication.xml
> file and the script ?
>
>
The parameter set in the
How this new architecture works with application-authentication.xml file,
say we have same parameter name with different names in
application-authentication.xml
file and the script ?
I guess we have completed an approach to get user inputs during the
authentication flow, can those user inputs
On Mon, Jun 18, 2018 at 11:04 AM, Maduranga Siriwardena
wrote:
> Hi Senthalan,
>
> "stepOptions" is gives a better meaning than "authenticationOptions" as I
> feel.
>
> Shall we rename the object key to "stepOptions"? Please suggest any
> better name, if the name "stepOptions" doesn't convey the
Hi Maduranga,
Yes, we will have 2 objects(authenticationOptions and authenticatorParams)
inside the 2nd parameter. I have done the implementation to support this
template,
executeStep(, { authenticationOptions : ,
*authenticatorParams : {local : : { : },*
*
federated : : { : }*
Hi Sagara,
I think "foo" : "alex" is a parameter passed to the authenticator. And yes,
if we can provide a little bit meaningful example it would be easier to
understand.
@Senthalan Kanagalingam , I was under the impression
that we are providing the parameters for the authenticators as a
Do we have authenticator with "foo" : "alex" ? when you provide sample
please make sure to provide sample closer to real world, please provide a
real example.
Thanks !
On Fri, Jun 15, 2018 at 6:56 PM, Senthalan Kanagalingam
wrote:
> Hi all,
>
> We are having an update in the structure of the
Hi all,
We are having an update in the structure of the basic syntax. Here is a
sample,
function onInitialRequest(context) {
executeStep(1,
{
authenticationOptions: {
local : {
"BasicAuthenticator" :{
[update]
hi all,
We had an offline discussion and decided to change the authentication
script syntax. We will be having an extra object in the 2nd parameter in
the executeStep which is introduced to filter the authenticators[1]. There
we can specify the authenticator and parameter
Hi all,
With an offline discussion we decided to change the definition from
parameter to property.
context.*property*.foo = "xyz";
and/or
context.*property*['foo'] = "xyz";
So in the authenticator we can access using getScriptProperty("foo");
thanks,
Senthalan.
On Mon, Jun 11, 2018 at 3:45 PM
Hi Pulasthi,
On Mon, Jun 11, 2018 at 11:36 AM Pulasthi Mahawithana
wrote:
> Hi Senthalan,
>
> On Mon, Jun 11, 2018 at 11:10 AM Senthalan Kanagalingam <
> sentha...@wso2.com> wrote:
>
>> Hi all,
>>
>> I am working on the $subject. The purpose of this implementation is to
>> have
Hi Senthalan,
On Mon, Jun 11, 2018 at 11:10 AM Senthalan Kanagalingam
wrote:
> Hi all,
>
> I am working on the $subject. The purpose of this implementation is to
> have application-specific configurations for authenticators. Currently, we
> can static configurations for the authenticators in
12 matches
Mail list logo
