Dear all, We have the following problem. There is an Appian infrastru

nikolaosm over 9 years ago

Dear all,

We have the following problem. There is an Appian infrastructure that is already installed and users of an organization have access to (green). In this infrastructure we already have some Appian applications deployed (green). We want to develop a new Appian Application (orange), and give access to that application to external (and internal) users. One solution we thought would be to setup a new infrastructure (red) that includes an HTTP server and an Appian AS (running tempo) and to put this in different zones in our network configuration. This will ensure that we will only open up Tempo to external users.
Using access right configuration on Tempo we can make sure that the new external users will be able to only access the new application we will develop. The problem is that (in this way) we also allow internal users to access this application (and other applications) externally. If the internal users use their internal credentials to ac...

Discussion posts and replies are publicly visible

Parents

0 nikolaosm over 9 years ago

We were actually thinking something like what you describe Alexey. I am pretty sure this is possible I wonder why shyamb says that this is not supported. I am not sure if they would like to switch all internal users to SSO authentication but that is one option. To davidwi, yes we are thinking of using the authorization of Appian to configure application access, record access etc. Now about Embedded Sail, we also looked into that but it appears that you have to do quite a bit of custom development. Essentially you are not embedding sail but you are developing a new client using the .js library provided by Appian. Not only that but the client you developing can never support records or reports. I am not sure I am so keen on embedded sail. The only advantage I can think of is that you are actually delegating authentication in embedded sail to an IdP so you can practically implement any type of authentication you would want. However this is because you are developing a new client.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 nikolaosm over 9 years ago

We were actually thinking something like what you describe Alexey. I am pretty sure this is possible I wonder why shyamb says that this is not supported. I am not sure if they would like to switch all internal users to SSO authentication but that is one option. To davidwi, yes we are thinking of using the authorization of Appian to configure application access, record access etc. Now about Embedded Sail, we also looked into that but it appears that you have to do quite a bit of custom development. Essentially you are not embedding sail but you are developing a new client using the .js library provided by Appian. Not only that but the client you developing can never support records or reports. I am not sure I am so keen on embedded sail. The only advantage I can think of is that you are actually delegating authentication in embedded sail to an IdP so you can practically implement any type of authentication you would want. However this is because you are developing a new client.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data