I can not find Security Provider Enforcer

#1

Hi,

I am reading the following link and try to do the same though,

I can not find Security Provider Enforcer…
28
How can I find it or how can I set the restrict rule?

Thanks,
Miwa

2019: The Year in Review
#2

@Miwa, have you saved the page and then refreshed the App Structure by clicking on the circle with the arrows in the top right hand corner?

56%20AM
Screen Shot 2019-10-07 at 12.41.56 AM.png862×246 14.4 KB

1 Like
#3

Yes, I have done it already.

Thanks,

#4

@Miwa, did that solve the issue?

#5

Nope…

After refreshing that circle, I got this problem…so…

#6

ok @Miwa, try closing the page and reopening the page.

Err wait, before doing that, is this a SPA page?

#7

I did it…but remains same…um…

yes, this is a SPA page.

#8

@Miwa are you trying to use the Security Provider Enforcer on the main SPA page or a content SPA page?

#9

I am trying to do this on a content page.

#10

Ok that makes sense now @Miwa. Security Provider Enforcer does not work on SPA content pages. See Secure SPA Sites for more information and tips and tricks about how to utilize separate public and secure SPA main pages.

Note: You can utilize more than one SPA and link the main pages together just like you would like together regular pages. For example:

Public SPA
-link to Secure SPA page

1 Like
#11

Thanks @scott, now I can see what’s your point!

I read through the link and try to make separate SPA pages then!

1 Like
#12

I have checked this out, on a new page it did not see the security provider option

I added an App ID and changed the App root from Body to Page and the security provider option appeared.
I could then freely change from App Root is Page or Body without losing the option
If i am correct I conclude this may be a bug but the workaround is easy, just temporarily change the app Root

1 Like
#13

I had the same issue and thought maybe it was removed, so I made another plan to make my own conditional statement. When I saved and closed the file, and then reopened the file a week later, I saw the enforcer option was available again. Lol. I have just left it, as my semi solution works for the silly little thing I was doing.

#14

Actually, I separated SPA as @scott mentioned.

However, when I access the restrict page, it doesn’t transit to signin page.
So restrict page doesn’t work…

44

49

12

Please tell me how to solve this problem!

Thanks,

#15

Can you give a link to a restricted page so I can view what is happening/ check code?

#16

@Hyperbytes

https://bestinx.me/voting/vote/sethbrogan

this is a restricted page.

Thanks,

#17

Where are you placing the restrictions, nothing in sethbrogan.php to show any restrict?

#18

sethbrogan.php is a SPA content page.

I did restrict setting on page.php.

After setting, the content of sethbrogan.php doesn’t appear, which is good.
But it doesn’t jump to singin.php…this is current problem.

#19

12
スクリーンショット 2019-10-08 13.25.12.png761×132 9.58 KB

#20

Still trying to get my head around exactly what the issue is.

Nothing wrong with page.php, if you call it directly (https://bestinx.me/page.php) the security provider works correctly and you are redirected to the signin page.

I guess the issue is your routing, not the security providers

sethbrogaqn seems to be a content page of page.php so the security enforce works correctly on page.php consequently the sethbrogan link can only be seen by a user with the correct credentials i.e. logged in as the page is protected.

Are you trying force a security redirect if someone tries to bypass the security on page.php and run https://bestinx.me/voting/vote/sethbrogan directly?