In the last, we do have looked at an error, which is Traw, whenever we try to submit a contact to
the backend application, we know contact is a open part and there is no security is needed to access
that.
And we also implemented all sort of token.
But still we are getting a four zero three four billion error due to CSIR official.
This is due to where we logout for security reasons inside the Lakota company, not because we are clearing
all the sition storage like the user details on the access token that we got from the backend application,
which is expected.
And there is no guarantee also that user will always log in to the application before accessing contact.
So in such scenarios where the user directly going to the contact page and posting his message, we
may not have access because we are getting out of broken only during the logging time and storing it
to the station storage.
And there is no need also for handling CSIR issue for the contact page because it's open to anyone and
anyone can push data to that backend database because that is expected business functionality.
So Forsett scenarios when you want for a few pages, Casarett should be ignored and for a few pages
CSIRO should be implemented.
We can always leverage spring security features provider.
Let's try to go to the back and call here.
We have declared SRF has to be enabled and that has to be for all the pods using this CSR token repository.
But if we have a scenario where for a few bars you don't want the authorities to be enforced, we can
always call ignoring and demand and define the we want to know in this scenario.
We don't want any CSR to be applied for the contact pod misconfiguration indicate the CSR should not
be enforced for contact page, but for all other pages and requests it has to be enforced and it uses
CSR token repository.
We conflict with this.
We should all that error.
Let's try to restart the server and going to the UK launching the browser.
So now I'm directly going to the contact us page.
So in this scenario, we never had a sort of token for the UI application and it never stored inside
this machine storage.
I'm trying to fill the data.
It's connected to me is the subject and messages regarding.
Oh no, as soon as I clicked, send a message, you can see your messages requestor and there is a reference
ideal's a generator.
We can also validate by going into the database, now into the database to call the contact message
table.
And this is the message that I have posted, and this is a service that got generated.
So with this, we looked at how to resolve the Assaraf issue by disabling it, by having a token retreat.
And at the same time, we also saw the mixed approach where for certain parts we don't want CSR to be
enforced.
And for other parts, CSR has to be followed.
Let's try to wrap up this section by looking at the summary of the section in mixed review by.