3. Portal Security
In this lecture, we’ll talk about portal security. So, this is related to the objective of configuring portal security, including web roles and page access. So, this is the first slab we’ll do. These are the steps. We’ll add a web page with a list component that shows account entities. So we’ll add a web page to show account entities or account rows. Then on that web page, we will enable entity permissions to restrict account viewing to authenticated users only. We’ll enable entity permissions so that only authenticated users can see that information. The new user’s ability to use local authentication will then be restored on the same portal. So, these three steps are on the webpage. Then we’ll go through the model-driven app, and there we’ll create a web browser record. Then, to grant global leads access to account centricity, we will create a table permission record. Then we will link our portal user to the web role and link the web role to the table permission. And then we’ll confirm that only authenticated users have access to all the account information. And if you are not logged in, you don’t have access to the account information.
So, coming back, this is our power app, and this is our portal, PL 200. Once we go to the portal and look at pages, I have added an account page. I’ve added a list to this account page, and this is the list on the list. I have given it a name, linked it to the accounts entity, and made it view all accounts. Then I started working on permissions. I have enabled table permissions. Then, after going to a browser to browse, I registered a new user using local authentication.
So, if you go to the sign-in option here or if you go to register here, I have registered using a local account email username and password. Then, going back to the power portal, I clicked on portal management, which took me to portal management, and I created a web role. So, these are the web roles I created a web role for. So I named it “account entity web role.” I linked it to our website, and that’s all I did. Then I created table permissions. So I created account table permissions, linked them to account tables, linked them to our website, and gave them access to global permissions. So we have these four options. global contact, account, parent, and self Five options. I gave it global permission, then I gave read access to it, and that’s it. Then I linked the portal user to the web role.
So if I go to the web role and go to related contacts, I’ve added my portal user, which I registered here, to this web browser. Then I linked table permissions to which I had just created this web browser. Now, when I go back to my browser and go to the accounts page, you see that I don’t have permissions, but if I sign in using my ID, which I just registered, and go to the accounts page, you see that I have access.
So this is the lab that we just completed. So Microsoft PowerShell and server security are configured primarily around database contact records. A contact record can represent a stakeholder, such as a customer, partner, supplier, supporter, or organisation employee. So we created a new record quantity code named Sirech. Now, on the webroles screen, we created a web role; you give it a name; you give the name of the web role website; we say we have a bull for authenticated users and anonymous users. That is, if users are authenticated, control will be applied to authenticated portal users; if they are anonymous, control will be applied to anonymous portal users. So these three Web services were already defined by default. And if you go into any of the web roles, you see name, website description, authenticated users, and anonymous users. So this is how you grant access. So contact is linked to a web role. So we did this: contact is linked to a web role, which is linked to table permissions, which are linked to table.
This is how you grant access to a database entity or table. You can also have a contact link to webcrowdlink to the web page access control rule, which will give access to a web page. So this is a screenshot of a web page control rule where you create a web page control, give it a name, link it to a website, link it to a web page, and give it a value. So, we can take a look here under the web page control rule. This is a web page control rule, and you give it a name, link it to a website web page, and give it rights. So this is how you control access to a page. And in the lab, we have seen that we are controlling access to an entity or table. So when you created table permissions, we had defined a scope. In table permissions, we defined access types and scopes. So we have these five options. If you define a global scope, we’ll have access to all the records in the table. If you have contact scope, then only records that are related to a user’s contact record will have rights. Account scope means records that are related to the user’s account. Parent scope means it has access to all the children of the parent, and cell scope means the user has their own contact record. So here we talked about the security of our portal. Thank you.
4. User Authentication
In this lecture, we’ll talk about portal user authentication. So when you create a portal for your power apps, then you have various options to authenticate the users who come in, register, and use your portal. As a result, it is recommended that you use as your Active Directory B to C identity provider for user authentication. To sign in, one of the options is to use the locallocal username and password. So this is your sign-in with your local account; another one is external social provider users’ sign-in through third-party identity providers. Here, you have options for signing in using Facebook, Google, Windows Live, Yahoo, etc.
Another method is to use an invitation code. So you generate an invitation code for your contacts and send them mailers with the invitation code, and then the user can log in using that invitation code. As a result, invitation codes indicate a refusal to accept pre-populated contact records. Then on the user authentication screen of the portal, you can enable two-factor authentication with email, you can have your email address confirmed, and you have an option for password recovery. So this is about portal user authentication using local social media and a referral code. Thank you.
